I started with an Afternoon Breeze (https://www.afternoonlabs.com/breeze/). I have since built a Sofle RGB (https://josefadamcik.github.io/SofleKeyboard/build_guide_rgb.html), with a second Sofle RGB planned to leave at the office.

I’m using Autorestic, a wrapper for Restic that lets you specify everything in a config file. It can fire hooks before/after backups so I’ve added it to my healthchecks instance to know if backups were completed successfully.

One caveat with Restic: it relies on hostnames to work optimally (for incremental backups) so if you’re using Autorestic in a container, set the host: option in the config file. My backups took a few hours each night until I fixed this - now they’re less than 30 minutes.

I use it to synchronise RetroArch save states across my devices - desktop PC, Android TV, and Android handheld.

I’ve done a couple of host migrations since using Docker for all my services.

I don’t even bother with database dumps or anything like that, I copy my compose files and mapped directories, being sure to preserve permissions, and all my services come back up without any issues.

@SeeJayEmm I totally get it. Learning curves can be brutal.

I just swapped from Ubuntu to Debian but I don’t use VMs - only containers. I back my files up directly to B2 using autorestic, also running in a container that is scheduled by… another container (chadburn).

No need for any VMs in my house. I honestly can’t see the point of them when containers exist.

Since I started posting online under my real name, I’m even more careful about what I post.