93ec260298
Stoat shipped with no account and no way to make one from LibrePortal. It is first-come-first-served, with invite_only=false, no captcha and no email verification, so every install left a window between the API answering and someone signing up in which anyone who could reach the port could take the instance. The installer now claims the configured account as soon as the API responds, and prints the credentials instead of "go and register". Provisioning goes over HTTP, not Mongo: an account needs a login AND a completed onboarding (accounts holds one, users the other) and passwords go through Stoat's argon2 layer. Failure is deliberately non-fatal — it leaves the instance exactly as it was before this existed, which must not fail an otherwise good install of sixteen containers. Both obvious config defaults are rejected by Stoat, which is only visible as a failed install, so both are chosen against its rules: example.com comes back DisallowedContactSupport (reserved domain) hence admin@stoat.local, and "admin" comes back InvalidUsername (reserved) hence "administrator". Two of the three missing adapter operations are now implemented: - createUser: create, log in, complete onboarding. Without the last step an account can sign in and then sits on a pick-a-username screen forever. - setPassword: previously excluded because hand-rolling argon2 risks writing a hash nothing can verify, locking the holder out with no error at the time. That objection is answered by refusing to hash at all — authifier already owns a reset flow, so this writes only its password_reset token to Mongo and lets PATCH /auth/account/reset_password do the hashing with the same code that verifies. Verified: reset by username and by email, new password logs in, token consumed. setAdmin is still NOT implemented, and the header now says so with evidence rather than assertion. Stoat has no instance-level admin flag: the user document holds only _id/username/discriminator and GET /users/@me adds only relationship and online. Permissions are per-server bitfields on server_members. A "make admin" button would invent a concept the app does not have. Also fixed two things found while testing: - post_start returned early when the public URL needed no settling, which skipped everything after it — so provisioning would have been silently missed on exactly the domain-backed installs that guessed the URL right. - _stoatBaseUrl advertised $public_ip_v4, the WAN address from an external resolver, in URLs compiled into the web client. Same fix as the APP_URL processor: prefer $local_ip_v4, since LibrePortal never forwards ports. Verified end to end on a clean install: the owner account is created and onboarded, the generated password logs in, both new tools run through `libreportal app tool`, and a created account survives a password reset. 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.