

1·
9 days agoReal selfhosters know
Real selfhosters know
Just remember the KISS principal: Keep It Simple, Stupid
Keep the NAS as a NAS, and I would honestly trim down everything else into a clustered hypervisor setup (like Proxmox) with dedicated VMs to run each stack. That way if you need to take a machine down for whatever reason, you can migrate its VMs/containers to another machine, with minimal downtime, so you can do whatever it is you need to do with said machine.
Full disclosure: this is what I do. I was in your shoes before.
I tried spinning up my own Lemmy instance. Everything was configured properly, but I could not get it working. Mind you, I run lots of things that take more than a drop-in compose.yml, so I’m not sure what I was doing wrong 🤔