Matthias Liffers

Like some others, I have separate storage and compute servers.

The data directory is an NFS share on my storage server and I run Nextcloud in docker on my compute server.

I have the NFS share defined as a volume of type nfs in the docker compose, mounted to /var/www/html/data. Nextcloud itself just treats it like a local directory.

I really like KitchenOwl’s shopping list interface, native iOS app, and OIDC integration. I haven’t used the budgeting or meal planning functions yet.

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.

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.