On the other hand, having one home server that does it all has its advantages. I have a mini PC with an N100 processor and two HDD drive bays. It hosts my Docker containers and holds my data. As long as you install all the software on the internal drive and keep only the data on the HDDs in RAID, you should be pretty safe. I hope. So far I’ve managed not to fuck it up.
Comment on I can not over express how happy I am with having setup my NAS from scratch.
lka1988@sh.itjust.works 5 days ago
It’s best of a NAS remains as a dedicated NAS and nothing else, that way if you’re experimenting and fuck something up, it doesn’t take your data with it when it goes down. I would build a separate machine to tinker with; share the appropriate folders on the NAS with whatever service(s) you’re running.
Diplomjodler3@lemmy.world 5 days ago
lka1988@sh.itjust.works 5 days ago
I wouldn’t mind that, but I have a bad habit of over-tinkering with the system files. Having Proxmox as a base where I can spin up VMs and containers to fuck with to my heart’s content is far more ideal in my situation. Plus, my entire cluster - NAS included - pulls 100-120 watts.
just_another_person@lemmy.world 5 days ago
This, plus also it’s good to revisit your setups from time to time to audit and improve.
lka1988@sh.itjust.works 5 days ago
Oh I’m always doing something with it, it’s basically my winter hobby haha. I’m currently building a “new” NAS out of an old HP Proliant G2 case (from like 2002) and 7th gen Intel hardware, to replace the current Mac mini/4-bay Sabrent DS-SC4B. Still gonna keep it running OMV, because it’s awesome, but the USB connection between the Mac and drive station is cumbersome.
Lichtblitz@discuss.tchncs.de 5 days ago
That’s what containers are for. Fucking up the container won’t fuck up the host. That was the best decision in self hosting I’ve done. Even that one virtual machine feels weird and uncomfortably legacy now but it needs to interact with hardware in a certain way that just won’t fully work with docker.
sugar_in_your_tea@sh.itjust.works 5 days ago
That’s what I’m doing. Here’s my setup:
It’s incredibly unlikely that I’ll mess anything up on the host, but I can always reinstall if needed.
greyfox@lemmy.world 4 days ago
If your NAS has enough resources the happy(ish) medium is to use your NAS as a hypervisor. The NAS can be on the bare hardware or its own VM, and the containers can have their own VMs as needed.
Then you don’t have to take down your NAS when you need to reboot your container’s VMs, and you get a little extra security separation between any externally facing services and any potentially sensitive data on the NAS.
Lots of performance trade offs there, but I tend to want to keep my NAS on more stable OS versions, and then the other workloads can be more bleeding edge/experimental as needed. It is a good mix if you have the resources, and having a hypervisor to test VMs is always useful.
lka1988@sh.itjust.works 5 days ago
I’ve done this before. That’s why I have a Proxmox cluster separate from my NAS now.