How our production deployment ships and runs: image builds, promotion lanes, the two environments, secrets and the auth path. This page describes one way to run rgxr (ours), not a requirement: rgxr itself needs only the web server, the API and Postgres, and works anonymous by default with no SSO at all. The Kubernetes manifests and the Kargo/ArgoCD wiring live in the GitOps repositories, not here; this page documents the contract between them and rgxr.
| Environment | URL | Tracks |
|---|---|---|
| Test | https://rgxr-test.yhkze.net | the master image tag (mutable) |
| Production | https://rgxr.yhkze.net | vX.Y.Z release tags (immutable) |
Both environments are the same chart: rgxr-web
(SvelteKit, adapter-node) plus rgxr-api (axum) behind
Traefik, with Postgres beneath. The API is stateless and scaled
horizontally. Postgres is a CloudNativePG cluster (rgxr-pg,
one instance on Ceph RBD) that archives WAL and takes daily base backups
to Ceph RGW; the API connects through rgxr-pg-rw.
CI builds both images on every push to master and on
v* tags, and pushes them to GHCR:
ghcr.io/yuuhikaze/rgxr-api: built from
api.Dockerfile (context: repo root), with graphviz and the
LaTeX toolchain baked inghcr.io/yuuhikaze/rgxr-web: built from
web.Dockerfile (context: web/), the
adapter-node server that forwards /api to the APITags: the branch name (mutable, test lane), v{{version}}
(release lane) and the bare commit SHA. After the push, CI notifies the
Kargo receiver; each Warehouse also polls, so a missed webhook only
delays promotion.
flowchart LR
CI["Forgejo CI<br/>api.Dockerfile · web.Dockerfile"] -->|push| GHCR["GHCR<br/>rgxr-api · rgxr-web"]
GHCR --> W["Kargo Warehouses<br/>(webhook + 5 min poll)"]
W -->|master| T["test lane<br/>auto promotion"]
W -->|vX.Y.Z| P["prod lane<br/>promoted by hand"]
Secrets are seeded in OpenBao (mount rgxr/) and wired
into the cluster via ESO ExternalSecret → K8s Secret →
container env. Only secret-bearing values take that path; the
RGXR_* flags and RUST_LOG are plain chart
values.
| Path | Keys | Used by |
|---|---|---|
rgxr/postgres |
password |
Postgres owner + API DATABASE_URL |
rgxr/backup |
access-key-id, secret-access-key |
Barman Cloud backups to Ceph RGW |
This is our deployment’s choice, not a rgxr dependency: sign-in goes
to the public realm of the yhkze Keycloak
(https://id.yhkze.net/realms/public), where anyone can
register and operators sign in with their yhkze account. Its client
rgxr is public with PKCE and an audience mapper, declared
in the nixos repo’s tofu/keycloak/public.tf. Both
environments run with RGXR_ANONYMOUS_FALLBACK=true, so
signing in stays optional. Details in Reference.