• 0 Posts
  • 44 Comments
Joined 1 year ago
cake
Cake day: September 1st, 2025

help-circle

  • You can use the per-user reverse proxies as a bridge between the host network and the user-specific internal network. So for a user coming from outside the path looks like this:

    User -> main reverse proxy on main IP and port 80/443 -> user-specific proxy listening on main IP with port 8080 and proxying to user-specific internal network -> destination container listening on user-specific internal network.

    And for a container running as a different user the path will be the same, but the user-specific reverse proxy will be listening on port 8081 and higher for example.


  • The solution to this can be multiple reverse proxies. Each user runs it’s own reverse proxy (if you actually need one, otherwise you let the container bind directly to a port on the host system). Then you run one main reverse proxy on port 80/443 that proxies to those other ports based on hostname.

    The upside of this construction is that containers running as different users can’t directly access each others internal networks, which is much better for security, as those networks often contain barely protected services, which is why you’re using a reverse proxy in the first place.

    Edit: there are different options with custom networks and such, but they’re even more complicated so I wouldn’t advise them.



  • One of the main advantages of Optane doesn’t easily show in a benchmark: it doesn’t have to do any cleanup. Normal SSD’s cheat all the time by caching writes in DRAM and an SLC portion of the NAND. Usually that works fine and you won’t notice, but if you keep writing then at some point performance will plummet dramatically. Also, the SSD’s need a breather every now and then to rewrite that cached data to it’s final place, during which time performance is also worse.

    Optane doesn’t need any of that. You can write to it at max speed 24/7 and it’ll just take it and keep going, at ridiculously low latency. Perfect for handling large non-stop data streams, or workloads that need a guaranteed low latency (both for reading and writing). It’s a real shame the concept failed, the tech was fantastic.




  • Built my own server to be completely silent since it lives in my living room. Based on an Intel i3-12100 with some NVMe and 5x SATA SSD’s, and running tons of containers. Does about 18W most of the time and it could have been lower with a different motherboard.

    All the UniFi stuff (gateway, switches, APs) uses just under 50W though, so there’s little sense in spending more money on the server to shave off a few watts.


  • Servers are terrible for homelab use. They’re unwieldy, consume way too much power and as you’ve found they’re very noisy. My vote goes to selling the thing and getting a mini PC, an (old) laptop or building something quiet and frugal yourself. In the last case you might be able to reuse some parts you already have. But if cost is important almost nothing beats second hand mini PC’s in value for money.



  • SnapRAID offers an additional benefit over real RAID-like systems: it functions as a short-term backup. If you sync it daily like I do, that means that if you accidentally delete a bunch of files (old enough to have been synced, I.e. older than one day in my case) you can restore them from the SnapRAID parity.

    The reverse is also true of course: if you lose a disk you also lose today’s changes to that data. So it’s most suited to large collections of rarely changing stuff like photos and videos and music IMHO.





  • Yeah only for :latest containers, that’s true. It automatically runs a daily service to check whether there are newer images available. You can turn it off per container if you don’t want it.

    One of the nice things about it is that I have containers running under several different users (for security reasons) so that saves me a lot of effort switching to all these users all the time.






  • I use mergerfs (and snapraid because I do care about my data and want parity) on ext4 formatted disks. This is a much better way to use your disks if you’re mostly just storing media. RAID is for mitigation of downtime after drive failure, not for joining a bunch of (differently sized?) disks into one pool if downtime isn’t really a problem.