8a997e14dd
updaterSetAnchorVersion located the anchor by looking for a service literally named "<app>-service". That is a convention, not a rule: matrix names its anchor service matrix-synapse and stoat names its api. For those apps nothing matched, so the rewrite changed no lines and the upgrade aborted at step 2 with "could not set version" — after having already taken a snapshot. Dry runs never showed it because they return before that step. It now finds the anchor by its bare <APP>_VERSION_TAG sentinel, the same way updaterPrimaryImage does. It also moved only the anchor. Some apps are one product shipped as many images: stoat is nine stoatchat services released together, all on v0.15.1, expecting matching versions of each other. Stepping the anchor alone would have put api on v0.16 while events stayed on v0.15.1 — the exact mismatch that once justified keeping the app off automatic updates. The lock-step set is DERIVED from the compose rather than configured, because the compose already states it: a service moves with the anchor when it carries a version sentinel, sits on the SAME tag, and shares the anchor's registry namespace. Both tests are load-bearing and each rejects a real case — livekit-server is same-namespace but on its own cadence, for-web is pinned to a commit hash, element-web is a different namespace entirely, and mongo has no namespace at all. Verified against copies of five composes: stoat moves all eight sibling services and nothing else; matrix, rocketchat and nextcloud move exactly one image. Every sentinel that moved gets its CFG_*_VERSION key set, not just the anchor's, or the next config-driven regeneration would quietly pull the locked-step services back to the old version. One trap worth naming: quotes were stripped with sed 's/["\047]//g', but \047 is an octal escape awk honours and sed does not — in a sed bracket expression it is the literal characters \ 0 4 7, so it deleted every 0, 4 and 7 it saw and v0.15.1 arrived as v.15.1. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
LibrePortal
Your own private corner of the internet — free, open, and yours.
LibrePortal is a self-hosted platform for running the apps you rely on, on your own server: one-click installs, a reverse proxy with automatic SSL, rootless Docker, optional VPN routing, and a clean web dashboard to manage it all.
⚠️ v0.1.0 — early days. Expect rough edges while things settle.
Why LibrePortal
Too many services today treat your data as theirs to take — quietly overstepping boundaries that should never have been crossed. LibrePortal grew out of frustration with that: it's a way to run the apps you depend on on your own server, where your data stays yours. Privacy here isn't a feature to toggle — it's the whole point.
Free & open — forever
The entire platform is free software under the GNU AGPLv3. Self-host it and you get everything — every feature, no paywalls, no telemetry. See our Promise for exactly what that means.
What you get
- 📦 One-click self-hosted apps (Nextcloud, Vaultwarden, Jellyfin, Gitea, …)
- 🔀 Traefik reverse proxy + automatic Let's Encrypt SSL
- 🔒 Rootless Docker, CrowdSec, sane security defaults
- 🛡️ Optional VPN routing (gluetun) for any app
- 🖥️ A web dashboard to install, configure, back up, and monitor everything
Quick start
curl -fsSL https://get.libreportal.org/install.sh | sudo bash
This installs a versioned, checksum-verified release (Debian/Ubuntu, root). Put
data on separate disks with --system-dir= / --containers-dir= / --backups-dir=.
The
get.libreportal.orghost is still being set up — until it's live, build a release and install from it locally (see the docs below).
Documentation
- docs/guide/install-and-use.md — install, place data on separate disks/drives, update, back up, uninstall.
- docs/contributing/development.md — run a dev copy, cut stable/edge releases, and test them before publishing.
LibrePortal Connect (optional)
Self-hosting is free and complete. If you'd rather not fiddle with the tricky parts — like reaching your server from your phone, or keeping off-site backups — LibrePortal Connect will handle them for you. Here's the catch that makes us different: we work like a courier carrying a sealed box. We move your data between your devices and store backup copies, but it stays locked and you hold the only key — we can't open it, and we never run your apps for you. Everything we offer, you can also set up yourself for free. Our Promise spells out exactly where that line sits.
Contributing
PRs welcome — see CONTRIBUTING.md. We use a lightweight
DCO sign-off (git commit -s), no CLA.
Acknowledgments
LibrePortal has been built from scratch since 2023. Its spark of inspiration
was a small installer script from Brian McGonagill (OpenSourceIsAwesome):
gitlab.com/bmcgonag/docker_installs.
From that seed it grew start to finish — refined, extended, and refactored
into the platform it is today.
License
GNU AGPLv3. What's open stays open.