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.
Hook it up with ChatGPT and you are golden!
Use a passphrase (not a password) and a physical security key, like a yubikey. It also supports TOTP or whatever 2fa Proton uses, you just connect it with a laptop or phone and it gives you a key.
A physical key is much more secure than 2fa from a password manager (although both are probably fine)
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:
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.
Oh, i did not know. Thanks!
No problem! I'm glad you got it working!
I would just pull the first filament away from the bed and the rest usually follows along and you get a little birds nest.
I barely use a calculator, but you could try SageMath if you like the thought of writing you math in Python.
I mean inserting the pause gcode command in the slicer. The idea is that this command is very basic, so every printer supports it, as opposed to a filament change command.
I used Cura and IIRC you could add "move away from the print and move back when unpaused" commands.
I haven't 3d printed for far too long, so my memory is very blurry. You might be better off looking for a Youtube video or googling for a tutorial, but it wasn't rocket science once someone on the internet explained it to me.
You can also just pause it and change filament manually.
Just remember to push through some of the filament until the color comming out is right.
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!