Gitea is retired; current-state prose in SCOPE, INTENT, README, AGENTS and rules now says Forgejo. File names, chart/resource names, the .gitea/workflows path and historical records are unchanged. Adds a forgejo-status alias and warns that gitea-deploy is not the live release source (railiance-apps forgejo-values). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Assistant: claude-code Assistant-Model: opus Assistant-Process: 99543@bnt-lap001 Assistant-Session: 05d24177-20b9-4e96-a91b-b73be1d6e99e
1 KiB
1 KiB
Stack
- Language: Helm values + Kubernetes manifests, Bash Make targets
- Key deps: Forgejo 11 (current forge runtime, deployed with the Gitea Helm chart), Actions runner substrate, SOPS/age; runs against the S2 cluster on railiance01
Dev Commands
make help # list all targets
make check-tools && make check-sops # preflight (read-only)
make gitea-status # forge runtime + database state (read-only)
make runner-status # Actions runner / registry probes (read-only)
make registry-docs | evidence-docs | runner-docs # print canonical docs
make gitea-deploy | gitea-ingress-deploy # production-touching
The gitea-* target names are kept for compatibility; the forge is Forgejo.
make forgejo-status is an alias for gitea-status. Do not run gitea-deploy
without review: the live release source is railiance-apps/helm/forgejo-values.yaml.
gitea-deploy / gitea-ingress-deploy change the production forge —
operator approval required. Status and docs targets are read-only.