

This is where I’m at too. If I go crazy and start installing stuff natively to experiment I end up with extra stuff auto configured that’s no longer needed and random problems I’m too lazy to figure out how to solve. Flatpak doesn’t do that and I don’t have to worry about that. I can install random stuff to play with and uninstall it cleanly. Some packages need more system access than flatpak gives natively and with those I’ll make the decision of if I want to set it up and tear it down manually or not.
Storage is cheap, my time not so much.
Generally desktop hardware is surprisingly power efficient, especially with lower-midrange components. Right now my home server is running on an ewaste HP Elitedesk.
For software, I’d really go for a config that uses ZFS over EXT4 for the data storage. ZFS is so battle-tested that anything you might find you want or need to fix or change, someone else has already documented the same situation multiple times over. Personally I went with a config like Apalrd’s with using proxmox for a stable host OS with good management and to create the zfs pool, then a container running cockpit for creating and managing the shares.
Currently that server has a 800GB Intel Datacenter SSD for boot and VM storage, and 2x 4TB HDDs in a ZFS mirror for NAS storage, an with a i5-4590 it’s running 6 Minecraft servers via Crafty Controller, Jellyfin, the Samba shares and I’ve spun up other random servers and VMs as desired/needed without trouble. Basically all of the services which run 24/7 are in LXCs because running Debian VMs on my Debian host seems too redundant for my tastes.