Self-hosting
A LodeBase server is one binary, lodebase-server, plus Postgres and somewhere to keep file contents (a folder or any S3-compatible bucket). People sign in through an OIDC provider; the docs use authentik.
What you need
- A Linux host with Docker and the Compose plugin. A small team runs comfortably on 4 cores, 8 GB of RAM and a large disk (or bucket) for repo content. 4 GB works if you leave out the metrics stack.
- A domain, with DNS you control, and ports 80 and 443 reachable.
- Disk for repo content: roughly the size of your projects plus their history. Identical data is stored once, so history grows slowly for assets that change in parts.
The production stack
The release ships a Compose stack (lodebase-prod-<version>.tar.gz) with:
| Service | Purpose |
|---|---|
| Traefik | TLS (Let's Encrypt), routing, gRPC and big uploads |
| Postgres | LodeBase's and authentik's databases |
| lodebase-server | the server: web app, gRPC API, pipelines, GC |
| authentik | sign-in, groups, and protecting internal pages |
| Caddy | the homepage and a downloads site |
| Uptime Kuma, Prometheus, Grafana, Loki | monitoring (optional: COMPOSE_PROFILES=metrics) |
sh
tar xzf lodebase-prod-<version>.tar.gz -C /opt/lodebase --strip-components=1
cd /opt/lodebase
cp .env.example .env && nano .env # your email, admin username
./setup.sh # generates secrets, prepares folders and the firewall
docker compose up -d --buildIts RUNBOOK.md walks through DNS, the first sign-in, inviting people and backups step by step.
Keep the proxy out of big uploads
Point DNS straight at the server (with Cloudflare: DNS only, not proxied). Proxies like Cloudflare's cut uploads at 100 MB and interfere with gRPC. If you put your own reverse proxy in front, it must speak HTTP/2 to LodeBase (h2c), and must not time out long requests: with Traefik, entryPoints.websecure.transport.respondingTimeouts.readTimeout: 0.
authentik
LodeBase signs people in with a public OIDC client (PKCE, no secret) so the CLI, daemon, Unreal plugin and web app can all use it:
| Setting | Value |
|---|---|
| Client type | Public |
| Client ID | lodebase-desktop |
| Redirect URIs | Regex http://127\.0\.0\.1:\d+/callback, and strict https://<your app host>/auth/callback |
| Signing key | any certificate (RS256) |
| Scopes | openid, profile, email, offline_access |
| Access / refresh token validity | minutes=10 / days=30 |
The application slug sets the issuer: https://<authentik>/application/o/<slug>/ goes in LODEBASE_OIDC_ISSUER. The production stack creates all of this (plus lodebase-admins and lodebase-beta groups) from a blueprint on first start.
Running the binary yourself
Without Docker: create a Postgres database, then
sh
LODEBASE_DATABASE_URL=postgres://lodebase:…@localhost/lodebase \
LODEBASE_STORAGE=file:///srv/lodebase/objects \
LODEBASE_OIDC_ISSUER=https://auth.example.com/application/o/lodebase/ \
LODEBASE_OIDC_CLIENT_ID=lodebase-desktop \
LODEBASE_PUBLIC_URL=https://vcs.example.com \
LODEBASE_ADMINS=you \
lodebase-serverIt listens on :7420 (plain HTTP/2; put TLS in front) and runs its own database migrations on start. /healthz and /readyz are for health checks. Every setting: server settings.
Upgrading
Replace the binary (or the image) and restart; migrations run on start. Back up first (backup and restore).