• 11 Posts
  • 189 Comments
Joined 2 years ago
cake
Cake day: July 5th, 2023

help-circle




  • Right, the flexibility angle makes sense if using a typical root fs like Ext4 with or without LVM. That’s a reason I’ve always kept the OS separate. But with ZFS there’s unlimited flexibility. Separate datasets or volumes within the same storage pool are trivial. I could do root on ZFS on separate SSDs and get those benefits but it’s more complicated that slapping it all in a single pool. Then maybe use the SSDs for cache. :D
















  • As someone who’s done cloud infrastructure professionally, this is the right way to make a project for setting up self-hosted applications. Not writing a bunch of bash scripts and putting them behind some web UI. We have well established infrastructure/config-as-code systems that are the gold standard which runs most clouds out there. Ansible is one of them. That’s the right tool for this job and a ton of professionals understand it and therefore can easily contribute improvements for the ones who don’t to use. I’m unfortunatrly invested in SaltStack but I wouldn’t feel worried to deploy a (well reviewed) project built on Ansible. Then slap a web UI on it if you like but that should be another project that hooks uses this one.


  • Yes, but self-hosting does whatever the HOWTO, YouTube vid or AI slop the user follows tells them to do. If the user doesn’t know the basics, how could they know what an instruction for activating UPnP does or opening a NAT port does and why that might expose their data? Laymen don’t even understand what making theie stuff publicly accessible means. It might simply mean “Yay I can access my stuff on the go.” 😄

    If on the other had the user learns the basics, they can tell when a doc instructs them to do something dangerous and they can do something about it to avoid disaster.