48c78270a9
Resolves open question 1. The device becomes the organising concept and the two registries become roles on it, so a user with one drive holding both app data and snapshots stops seeing "bigdisk" twice meaning two different things. It extends a page that already exists rather than adding one: /admin/system/storage is currently the Docker disk breakdown, and webui_system_metrics.sh already builds a disks array from df. The view is that array enriched with lsblk -J -e7 (model, transport, rotational, removable — with -e7 dropping the ~15 snap loop devices a desktop box carries) and joined against both registries. The union is the part that matters more than the enrichment: a registered drive that is currently unplugged does not appear in lsblk at all, and that is exactly when someone opens this page. So rows come from the registry first and attached hardware second — a missing device still renders, marked not attached, naming the apps stranded on it. Rows key on fs_uuid, since /dev/sdb1 reorders across reboots and would scramble the table. This also gives every standing badge from §6/§6.1/§6.2 a natural home, because each is a property of the device rather than of either registry, and it turns "type the same path into two different pages" into actions on the row you are already looking at. Two limitations written down rather than discovered later: ZFS datasets report distinct st_dev but share a pool, so grouping by device over-reports free space (btrfs subvolumes are fine); and the page stays read-only about the system — it can show the fstab line to add, never add it. Phase 6 now builds this instead of a separate Storage page, which with disks as the frame would have reintroduced the split this resolves. Also folds in §10.5 — the dashboard gauge becomes a summary linking here. 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.