9a7df822dc
The compose rewrite assumed each app had exactly <type>-service and <type>_db. That holds for Bookstack and almost nothing else: cloning Nextcloud left -db, -redis and -web pointing at the ORIGINAL app's containers, and Matrix, Ollama, Mastodon, Owncloud, Gitea, Jitsi, Invidious, Rocketchat and Mattermost all had the same hole. Docker refuses a duplicate container name and two Traefik routers sharing a name fight over the host, so those clones could not have worked. Service identities are now discovered from the compose itself — its SERVICE_TAG_<n> markers plus its container_name values — and each is renamed. Verified across all 38 shipped apps: 15 are fixed, 21 produce byte-identical output to the old rule (Bookstack among them, so the running instances are unaffected), and 2 are refused. Details worth knowing: - Separators compare as equivalent, so the app dir libreportal_catalog matches its libreportal-catalog-* services instead of being wrongly refused. - Tokens are substituted longest-first through placeholders. \b has to end a token because per-port routers are named <service>-<portname> (traefik.http.routers.adguard-service-webui), which also means a short name could otherwise match inside a longer one — ordering is what prevents that. - Commented-out lines are not harvested. Several templates park an optional sidecar behind # (adguard-exporter, pihole-exporter, wireguard-exporter); renaming those also mangled the image name in the same block, leaving a trap for anyone uncommenting it. Commented image: lines are skipped too. - image: lines are genuinely excluded now. The old comment claimed service tokens "never appear in an image path", but libreportal builds a local image named after its own service and the old rule rewrote that reference. An app with a service carrying no <type> prefix (stoat's api/database/minio, prometheus's node-exporter/cadvisor) cannot be made unique mechanically, and rewriting a bare word like minio would corrupt image: minio/minio. Those are refused with an explanation and the partial clone is removed, rather than handed back as an instance that silently fights the base app. 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.