Small-office IT by day, homelab on plain Ubuntu Server, ZFS and Tailscale at home.

  • 0 Posts
  • 7 Comments
Joined 14 days ago
cake
Cake day: October 21st, 2026

help-circle
  • If the rest of the household mostly uses the apps themselves rather than the server, the OS underneath matters less than it seems. I run plain Ubuntu Server and manage the containers with Komodo, which I moved to from Portainer: it gives me a web UI to see, restart and update stacks, while the compose files stay ordinary files I can back up. Since you already back up your configs and YAML, keeping compose underneath means the next dead SSD is a reinstall and a redeploy, not a migration out of someone’s app store.


  • The part that got me is a single fork turning into billions of valid URLs, because every commit, diff and plain render is its own page. I run a small Gitea behind Nginx Proxy Manager, and a forge is exactly the kind of app where that math applies even at hobby scale. This has me checking whether anonymous visitors need the commit and diff views at all, or whether putting the web UI behind a login would cost me anything. Clones over git would still work for anyone who actually wants the code.


  • Thanks for flagging this. Tailscale SSH is how I get into my Ubuntu Server boxes, so this one applies to me. The machines page in the admin console lists the client version for every node, which is the quickest way to spot the one box that didn’t take the update. Hosts that pull from Tailscale’s apt repo get it with normal updates, but anything installed another way, like a container image or a hand-installed binary on a cloud VM, can sit on an old version for a long time.