No problem!

I hacked this together instead of going to sleep, so it might make your deck explode, but maybe it’s a starting point for you or someone else:

# home-deck-mounts.mount
#
# Mount units must be named after the destination path, this / replaced by -, like above
#
# This is a template unit.
# That's explained here: https://fedoramagazine.org/systemd-template-unit-files/
# TL;DR: run it like this `[email protected]` if you want to mount the subdirectory "linuxisos" from SHARE_PATH
[Unit]
Description=NetMount %I
After=graphical.target
# This is commented out, because it is implicit for network mounts https://www.freedesktop.org/software/systemd/man/latest/systemd.mount.html#Default%20Dependencies
# I keep it here as an example
#After=network-online.target
#Requires=network-online.target

[Mount]
# %i expands to what ever you put after the @ when starting/activating the service
What=10.10.10.99:/mnt/user/%i
Where=/home/deck/mounts/%i
Type=nfs
Options=exec

[Install]
WantedBy=default.target

I couldn’t confirm if mount units are allowed to be template units, but if not, just duplicate the service for each path and replace %i.

Say the word if you run into issues!

Don’t put yourself down! Using systemd wouldn’t make it work “better”, it’s just more “proper” (and a great tool to know in general!)

Great job and keep going!

This is really cool!

Where did you put the service file?

I don’t mean this as critique, but as possible next project, since your solution works perfectly fine. Systemd has some cool features that could make this project have a bit fewer moving parts:

• a .mount file could replace the mount and unmount script, and handle logging too! (I am pretty sure you would need separate files per mount, though, so “fewer moving parts” might be a bit of a lie, depending on your interpretation)
• that “After=” setting you used, can also be used to check for network connectivity. IIRC it’s “networking.target” on Fedora, at least. You might want to double check the systemd docs if After is the right one for this, as I have a hard remembering the systemd dependency intricacies.

That way you would end up with a .mount file per mounted directory, with logging using journald, and no external scripts.

I really like systemd as it can be a great tool, when you start to break down the complexity of it.

I hope you get well soon and get the best you can from this time.

Cockpit is great.

It’s pretty simplistic. It gives you an overview of your system ressources and handles libvirt VMs and Docker (i think. I used it with Podman, but in this context both should work).

My impression was that the container and VM interfaces were pretty simple, and I wouldn’t have liked it as my main interface for those services, but it would be perfect for getting an overview and restarting them!

Node-Red can do dashboards. I don’t know if it does data logging, but I would guess so since it can do dashboards. It also supports MQTT so it should handle ESPHome devices without a problem.

It’s made for automations (and great at it) but it can be a minimalist HA hub too.

I run the built-in automatic rpm-ostree upgrade service every 6 hours.

If you think that’s too inefficient, maybe read the docs for shutdown.target and see if you can use that to run an upgrade service before shutdown?

I’m not too experienced with that part of systemd but it seems like it could be a “proper” way to run things on shutdown?

Nextcloud doesn’t verify your email and has tons of other nice features as well. ProtonDrive (/ProtonMail as another user suggested) probably doesn’t or you could use your Proton address for that.

You mention allowing weak passwords are a plus. Please use a weak password, especially without email as 2nd factor.

Have you considered using mnemonics for your passphrase?

Generate a number (i would use around 5) of random words (EFF has a wordlist, humans are really bad at randomness) and link them together using silly images. For example:

• sparrow
• window
• automobile

First, you link sparrow to window: imagine a sparrow trying to break through a window, not just flying into it by accident, no, this sparrow is mad and is set to destroy it.

Second, you link window to automobile: imagine an automobile with huge windows. The car is completely normal sized except every window is at least 3 meters tall. It looks absolutely ridiculous and you feel embrassed that youvhave to drive it everywhere.

Repeat this proces for the rest of the words. It helps remembering them if the image makes you feel something, like making you chuckle or feel angry that you have to deal with this stupid contraption (only in your mind, hopefully)

Also, make sure each “link” is distinct. Eg. Don’t make the second link an automobile driving into a window when the sparrow does the same. It will mess up the order and make you jump around between similar mental images.

I only tried running rootless when i set them up several years ago and i was completely green, so it was probably me who was the problem.

Regarding podman-compose, Fedora repos has a a package that aliases podman -> docker and the regular docker-compose package, which i used before migrating to podman+systemd. It worked flawlessly unless i did networking shenanigans because Podman and Docker differs (/differed?) in so some thing simply couldn’t be brought over.

Edit: i found the docker-compose and Podman alias thingies in a Fedora Magazine post.

However, unless you use docker-compose a lot for other stuff, learning to use Podmans systemd integration (also called quadlet) is very much worth it. They’re just a really powerful combo and systemd has a ton of nice features for making stuff run and keep running.

Podman is CLI and API compatible with Docker (except where differences in implementation doesn’t allow it)

Running Podman as root is 99.9% the same as running Docker.

I have been running my homelab with Podman for several years and it is absolutely mature enough for a regular user.

Also, the docs are really good.

I barely use a calculator, but you could try SageMath if you like the thought of writing you math in Python.

Then use Bugzilla. That will show you are ready to flail yourself for the good of the company /s

Sorry, but i find that platform so painful to use.

On a more serious note, i think some of the “github-style” (Gitlab/Gitea/Forgejo) can migrate between each other.

Check out if that’s true and if so, try them all!

Forgejo/Gitea are probably the most common “low-resource” (read: doesn’t use a couple of GB RAM, like Gitlab supposedly does) code forges.

Do you want to impress future employers by running an enterprise-grade bugtracker or by showing that you can document your work with meaningful bug reports/etc.?

If it’s the first option, consider Gitlab, if it’s the second option, what ever you like.

There already good recommendations, so i’ll just add that you shouldn’t make your work life harder for the sake of running Linux.

Definetly give it a go, and see if it fulfills your needs, but maybe hold off on nuking your Windows install until you are satisfied.

I use my Linux computer for personal stuff and some work stuff (web-browsing, email, office suite) and i have a separate Windows PC just for running applications specific to my field, which don’t have Linux versions or alternatives (or where it makes the most sense for me to use the industry standard)

At least talk about.

That’s what she’s criticizing her western followers and the western media for not doing.

The thought that all the western world can do is to either declare war or sit on our hands is plain wrong.

“But not the oppressive government willing to imprison and kill her” FTFY

But it is hosted on your home server.

When you subscribe to a community, your home server downloads the content and passes it on to you.

This is not like when The Pirate Bay was allowed to live because it only hosted torrent files and not copyrighted content, in the fediverse, you copy the content to your own server, and pass it on to the client/user, which means hosting the content.

You already have some good suggestions, so i just want to mention openWRT which can be flashed on off-the-shelf router combo (just check their supported devices first, if you go this route)

By circumstance.

It was hard for me initially to switch over because i kept either creating or running into problems i couldn’t figure out how to solve.

This overlapped with the Snowden leaks and i got really interested in privacy and security which lead to me running Qubes OS[1] for a short while. It was a slow and almost painful experience since i didn’t actually have anything worth that effort to protect - but it got me over the edge and i wiped Qubes and reinstalled Fedora 23.

At the time i just liked the package manager better, for reasons that are no longer relevant.

Today i like it because it forces me into good habits of: figuring out what exactly is misbehaving > finding the official documentation or issue tracker for it > finding a solution or reporting the it to the developers.

Don’t tire yourself out with that in the beginning. Just do stuff you need or stuff that seems fun.

Protip: Learn how to use Toolbx or Distrobox to create a “sandbox”, (that’s both the technical term and a very descriptive one) that will make it easier to get back to a working state if you mess something up. Learn about and understand what it can’t get back to a working state. This will help keep you sane if you like to tinker.

1 A Linux-like operating system that only runs VMs and everything you do happens inside one of these. This way you can isolate you virtual “work computer” from your virtual “personal computer”, making it harder for malicious programs to access the rest if your data.

There are a lot of “linux for beginners” blogs/videos/whatever. They’re a good way to get an overview and learn the first steps. Don’t get into a rabbit hole, though. Watch a couple and start trying it out.

You can try out Linux distros in a virtual machine (VM). You’ll have to use your web-searching-skills to find a program that can run a VM as i can’t recommend one that runs on Windows.

That program runs the operating system on top of the one you have now, so you don’t need to reinstall over and over again while you find a distribution that works for you.

A distribution is what we call “a linux”. “Linux” is just a part of the OS, and a distribution combines it with other software to make something your computer can boot. If this is a bit confusing, don’t worry, it’s not important, you just have to remember the word “distribution” (or distro)

I use a distro called Fedora, but between that and Ubuntu and Linux Mint you should find one that works for you. Don’t overthink it. They all do the same job in slightly different ways, so just pick one and start using it for the stuff you usually use your computer for. Ubuntu is the easiest to search for help for, and Linux Mint is based on Ubuntu, so 99.9% of solutions will be the same for Mint. Distros not based on Ubuntu works with the same instructions 90% of the time, but that might be too annoying when you are justvgetting your feet wet.

Note that a lot of distros have multiple “editions”, “spins” or whatever they decided to call it. They mostly differ in the way your “desktop” is presented. Just look at some Youtube videos and some screenshot and try them out.

Now go use your computer with Linux. A lot of the initial friction is from having to learn stuff over again. Search the web for solutions and if you don’t find them ask for help.

Your distrobution’s forums are usually a good place to start, so is places like this. Try to give information you think might be relevant when asking for help and and help people help you by following their instructions and providing the information they ask for. Finding solutions to problems is like a seperate skill you need to train, so if it’s confusing or you feel dumb for not understanding something, don’t get discouraged, you’re just getting better.

Welcome to the Linix community, we hope you like it.