741edfdeb1
An app's deployed config is written once, on first install, and never touched again — dockerConfigSetupToContainer copies only when the file is absent, precisely so an update can never overwrite values someone has edited. Right default, unchosen consequence: an app that gains a CFG_ option in a new release has it on every fresh install and on no existing one. The failure is silent, which is the worst part. Nothing errors. The key reads as empty and whatever depends on it quietly does something else. Two halves, because there were two gaps. Per-app, when a config is set up, options present in the template and missing from the deployed file are appended with their comment blocks — the comment is the only explanation of a new option that exists, and a bare key at the end of a documented file is not actionable. And a sweep across every installed app after an update, because an update redeploys LibrePortal itself and nothing else, so without it a new option would reach an app only when someone next reinstalled it — which, for an app that is working, may be never. Existing values are never touched, and keys the deployed file has but the template no longer does are left alone: a removed option is usually a rename, and deleting someone's value is not recoverable. Deliberately not a regenerate-from-template, which would place new keys in their proper section and refresh the docs, but would put a whole-file rewrite of every app config in the path of every app action — appending cannot lose a line. Backfilled RANDOMIZED* defaults are generated in both paths. A placeholder left in place would otherwise be a credential identical on every install that took the upgrade. The sweep is driven from the template directory, not the container one: under rootless the container tree is drwxr-x--x and owned by the docker user, so the manager can traverse it but not list it, and a glob there expands to nothing — the sweep would report success having examined no apps. Run against this install it found real drift beyond the test fixtures: mattermost was missing CFG_MATTERMOST_ADMIN_PASSWORD, whose own comment notes that without it the password-reset tool has nothing to write to, and speedtest was missing its password key entirely. 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.