CaptainShardmind

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.

I keep my Docker app data on ZFS, with sanoid snapshots every 15 minutes and syncoid replicating hourly between two boxes, so plain file backup is mostly covered by the filesystem for me. Where a tool like this would still earn a spot is the database side, since a snapshot of a running Postgres isn’t the same thing as a proper dump. Does the Restic snapshot mode let you restore a single directory to a different path, so you can test a restore without touching the live copy?

Five minutes for a four-month rollback is quicker than I’d have guessed. Mirrored, underprovisioned D3s for boot is a nice way to stop worrying about that drive.

I’m on Symfonium with Navidrome, but automatic playlist download sync is the feature that would get me to try an open-source client. Does it keep a downloaded playlist in step when a Navidrome smart playlist changes on the server?

I’m not on OPNsense, but I lean on the same idea with my Ubuntu servers, and being able to roll back is what makes me willing to update at all. One thing I’d add: boot environments live on the same disk, so export config.xml somewhere off the box on the same schedule. And do one deliberate rollback before an update forces you to, so you know how long it really takes.