Ha, home has been traditionally always on a separate drive. That's the reason why root user has the home under /root and not /home/root, so that it can login even if the home drive didn't Mount.
As a curiosity, even /usr was traditionally on a separate drive and that's why critical binaries and libraries where under /bin and /lib while all non critical stuff under /usr. It is called "split-usr".
Nowadays /usr is always on the same drive as root, and we moved to a "merge-usr" approach where stuff under /lib and /bin is a symlink into /usr/lib and /usr/bin.
Because when HDDs where 50mb in size, even that small binary file counted as big :)
I have a 3,2,1 backup strategy with restic+backrest. One full backup local on an external disk. Second backup in the house on a disk mounted to an OpenWRT router in the garden, third backup remote on my vps. Backup is daily at night.
My external access is via a static public IP on a VPS I rent using a double layer of NGINX reverse proxy. Vps is connected to home via wireguard, so nobody has to complain that they require a wireguard VPN on their phones... WAF is critical here.
Maybe one would be sufficient, but for better separation and to have a single startup script for every service I prefer to keep them on different users.
In this way, also the data of each service is created with a different user and cannot be messed up by a rogue service...
And why let that user access root in any way? Even via sudo? No need. No risk.
One service one user. Simple security and separation policy
A lifetime old basic rule is never run anything as root, not even your podman :)
I only ever use rootless podman jn my system and I fond it pretty easy to actually run: zero effort whatsoever.
Why you say it's complicated?
Yes I always create one unprivileged user (not even in the sudoers or wheel group ofc) for every service I containerize. And create a dedicated network for the service too.
It only takes a few lines in a normal docker compose yaml.
Also I use docker compose on podman, yes docker compose not podman compose.
Edit: also podman play nice with iptables and nft (which should be always preferred nowadays) instead docker can mess your system good, and don't work with nft tables, unless quirks quirks...
Started with authelia. True, the learning curve might be steeper but for such a critical security wise component, well worth to invest into.
Simply love authelia so far. Documentation is great and detailed, but you need to study and understand.
Honestly, well worth it. I wouldn't go quick on something like that just to install it faster then risk some breach.