

Toss in another drive for RAID5. That way you can at least have some redundancy…
Toss in another drive for RAID5. That way you can at least have some redundancy…
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.
It’s best if a NAS remains as a dedicated NAS and nothing else; I would build a separate machine to tinker with, and share the appropriate folders on the NAS with whatever service(s) you’re running. That way, if you’re experimenting and fuck something up, it doesn’t take your data with it when it goes down.
One is a smaller chest freezer, about 3 feet tall, probably 6 or 7 cubic feet if I had to guess. The other is a Hamilton Beach upright freezer from Costco. Both are full, so that helps with keeping them cold.
Fair point.