Sample mattersEvery client, case, and document on this deployment is invented for demonstration. This is purposefully a demo environment.

Deploy the forge before switching repositories

Forgejo is an opt-in service per installation. It owns a separate forgejo database on the retained PostgreSQL server and a separate retained volume for repositories and other files. The release order prepares PostgreSQL, client logins, and migrations, then Forgejo's database and server, before the Navigator workloads.

Configure the installation's HTTPS root URL, DNS and TLS, its own OIDC client and callback, the verified-email domain allowlist, and PostgreSQL certificate trust. Keep Forgejo credentials in its encrypted service file:


navigator ops secrets apply --deployment "$DEPLOYMENT" --deployments-dir "$NAVIGATOR_DEPLOYMENTS_DIR" \
  --service forgejo --dry-run

Set DEPLOYMENT to the selected row in $NAVIGATOR_DEPLOYMENTS_DIR/deployments/. The service selector renders mounted-file Secrets; it does not deploy or restart Forgejo. Use docs/forgejo-deployment.md and docs/deployment-secrets.md for the prerequisites and ordered application.