From fa5d1af0a1fa43bdd74c1dafd86098b5d08ea7a8 Mon Sep 17 00:00:00 2001 From: tegwick Date: Sun, 18 Oct 2026 02:36:09 +0200 Subject: [PATCH] docs: name Forgejo as the current forge, keep gitea identifiers for compatibility 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 Assistant: claude-code Assistant-Model: opus Assistant-Process: 99543@bnt-lap001 Assistant-Session: 05d24177-20b9-4e96-a91b-b73be1d6e99e --- .claude/rules/repo-identity.md | 2 +- .claude/rules/stack-and-commands.md | 5 ++++- AGENTS.md | 2 +- INTENT.md | 11 ++++++----- Makefile | 14 ++++++++------ README.md | 2 +- SCOPE.md | 22 +++++++++++----------- 7 files changed, 32 insertions(+), 26 deletions(-) diff --git a/.claude/rules/repo-identity.md b/.claude/rules/repo-identity.md index 84122df..8b146e4 100644 --- a/.claude/rules/repo-identity.md +++ b/.claude/rules/repo-identity.md @@ -1,4 +1,4 @@ -**Purpose:** Railiance forge and artifact infrastructure: current Gitea operation, future Forgejo migration, container/package registries, runner substrate, artifact lifecycle, and forge operating evidence. +**Purpose:** Railiance forge and artifact infrastructure: current Forgejo operation (migrated from Gitea), container/package registries, runner substrate, artifact lifecycle, and forge operating evidence. **Domain:** financials **Repo slug:** railiance-forge diff --git a/.claude/rules/stack-and-commands.md b/.claude/rules/stack-and-commands.md index d3683f6..d2f60f9 100644 --- a/.claude/rules/stack-and-commands.md +++ b/.claude/rules/stack-and-commands.md @@ -1,7 +1,7 @@ ## Stack - **Language:** Helm values + Kubernetes manifests, Bash Make targets -- **Key deps:** Gitea (current forge runtime), Actions runner substrate, SOPS/age; runs against the S2 cluster on railiance01 +- **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 @@ -14,5 +14,8 @@ 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. diff --git a/AGENTS.md b/AGENTS.md index 54a2503..979a5a6 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -2,7 +2,7 @@ ## Repo Identity -**Purpose:** Railiance forge and artifact infrastructure: current Gitea operation, future Forgejo migration, container/package registries, runner substrate, artifact lifecycle, and forge operating evidence. +**Purpose:** Railiance forge and artifact infrastructure: current Forgejo operation (migrated from Gitea), container/package registries, runner substrate, artifact lifecycle, and forge operating evidence. **Domain:** financials **Repo slug:** railiance-forge diff --git a/INTENT.md b/INTENT.md index d8f251b..ce63be7 100644 --- a/INTENT.md +++ b/INTENT.md @@ -33,7 +33,7 @@ This layer exists to make those responsibilities explicit and operable. > *Where we are going.* To become the **canonical home for Railiance forge and artifact infrastructure** -- current Gitea operation, future Forgejo migration, container and package +- current Forgejo operation (migrated from Gitea), container and package registries, forge-backed automation runner substrate, artifact lifecycle, and forge operational evidence. @@ -76,11 +76,12 @@ promotion evidence. Forge data is operationally critical. Source repos, packages, registry blobs, and runner state need explicit backup and restore posture. -### 6. Current Gitea, Future Forgejo +### 6. Forgejo Is the Current Forge -Gitea is the current workload; Forgejo is the intended production direction. -The repo should support both the current operating state and clean future -cutover planning. +Forgejo is the production forge; the earlier Gitea workload is retired. +Some chart, resource and path names still say `gitea` for compatibility; +the repo treats them as Forgejo infrastructure and keeps future forge +changes cleanly plannable. --- diff --git a/Makefile b/Makefile index bfbd6cc..464cef3 100644 --- a/Makefile +++ b/Makefile @@ -50,7 +50,7 @@ evidence-docs: ## Print forge evidence and handoff contracts sed -n '1,260p' "$$doc"; \ done -runner-docs: ## Print Gitea Actions runner substrate docs and evidence +runner-docs: ## Print Forgejo Actions runner substrate docs and evidence @for doc in $(RUNNER_DOCS); do \ printf '\n## %s\n\n' "$$doc"; \ sed -n '1,260p' "$$doc"; \ @@ -89,18 +89,20 @@ check-runner-tools: ## Check local tools used by runner inspection targets done; \ exit $$missing -##@ Current Gitea +##@ Current Forgejo (target names keep the legacy gitea- prefix) -gitea-deploy: ## Deploy / upgrade current Gitea forge runtime +gitea-deploy: ## Deploy / upgrade the Forgejo runtime via the Gitea chart (review first: live source is railiance-apps forgejo-values) helm upgrade --install $(GITEA_RELEASE) $(GITEA_CHART) \ -f <(sops -d $(GITEA_VALUES)) \ -f $(GITEA_REGISTRY_VALUES) \ --namespace $(GITEA_NAMESPACE) --create-namespace -gitea-ingress-deploy: ## Apply the public Gitea HTTPS ingress +gitea-ingress-deploy: ## Apply the public Forgejo HTTPS ingress kubectl apply -f $(GITEA_INGRESS) -gitea-status: ## Read-only status for current Gitea runtime and database +forgejo-status: gitea-status ## Read-only status for Forgejo runtime and database (alias) + +gitea-status: ## Read-only status for Forgejo runtime and database kubectl get pods -n $(GITEA_NAMESPACE) -l app.kubernetes.io/instance=$(GITEA_RELEASE) kubectl get svc -n $(GITEA_NAMESPACE) $(GITEA_HTTP_SERVICE) --ignore-not-found kubectl get svc -n $(GITEA_NAMESPACE) $(GITEA_SSH_SERVICE) --ignore-not-found @@ -120,7 +122,7 @@ help: ## Show this help /^[a-zA-Z0-9_-]+:.*?##/ { printf " \033[36m%-20s\033[0m %s\n", $$1, $$2 } \ /^##@/ { printf "\n\033[1m%s\033[0m\n", substr($$0, 5) }' $(MAKEFILE_LIST) -.PHONY: check-tools check-sops registry-docs evidence-docs runner-docs runner-status forgejo-runner-status forge-observe test-unit check-runner-tools gitea-deploy gitea-ingress-deploy gitea-status help +.PHONY: check-tools check-sops registry-docs evidence-docs runner-docs runner-status forgejo-runner-status forge-observe test-unit check-runner-tools gitea-deploy gitea-ingress-deploy gitea-status forgejo-status help ##@ Secret detection diff --git a/README.md b/README.md index 026e3ef..63333b5 100644 --- a/README.md +++ b/README.md @@ -15,7 +15,7 @@ Start with: 5. `workplans/` Current implementation status: active forge extraction. Canonical registry -operation docs, runner ownership contracts, deploy-capable Gitea files, and +operation docs, runner ownership contracts, deploy-capable forge files, and operator targets live here now. No live Helm deploy or Kubernetes apply was run as part of the move. diff --git a/SCOPE.md b/SCOPE.md index f83551f..36cccd5 100644 --- a/SCOPE.md +++ b/SCOPE.md @@ -3,14 +3,14 @@ This file defines what `railiance-forge` owns, when to use it, and where its boundaries stop. -Last reviewed: 2026-08-22 +Last reviewed: 2026-10-18 --- ## One-liner -Forge and artifact infrastructure for Railiance: current Gitea operation, -future Forgejo migration, container and package registries, Actions runner +Forge and artifact infrastructure for Railiance: current Forgejo operation +(migrated from Gitea), container and package registries, Actions runner substrate, artifact lifecycle, and forge operational evidence. --- @@ -30,7 +30,7 @@ The practical contract is: 4. `railiance-apps` consumes forge artifacts and deploys user-facing workloads. Canonical registry operation docs and read-only forge checks now live here. -Deploy-capable Gitea Helm/SOPS/manifests also live here now; `railiance-apps` +Deploy-capable forge Helm/SOPS/manifests also live here now; `railiance-apps` keeps only transitional compatibility wrappers for old operator entry points. The runner, Actions, and GitOps ownership contract lives in `docs/ci-runner-actions-gitops-ownership.md`. @@ -45,7 +45,7 @@ The Fabric graph declarations for forge capabilities and edges live in ## In Scope -- Current Gitea operation and future Forgejo migration/cutover planning. +- Current Forgejo operation (migrated from Gitea) and future forge change planning. - Source forge deployment configuration and runbooks. - Container registry and package registry enablement. - Registry storage posture, cleanup, retention, and restore readiness. @@ -89,8 +89,8 @@ The Fabric graph declarations for forge capabilities and edges live in ## Relevant When -- Operating or upgrading Gitea as the current Railiance forge. -- Planning or executing a Forgejo migration or cutover. +- Operating or upgrading Forgejo as the current Railiance forge. +- Planning or executing a forge upgrade, migration or cutover. - Enabling or debugging container/package registry behavior. - Defining artifact retention, cleanup, provenance, or restore posture. - Deploying or operating forge-backed Actions runners. @@ -115,9 +115,9 @@ The Fabric graph declarations for forge capabilities and edges live in - Status: active forge operation with explicit S4 consumer-contract handoff. - Implementation: repository contract, registry docs, initial operating - contracts, deploy-capable Gitea files, and operator targets are present. + contracts, deploy-capable forge files, and operator targets are present. - Stability: emerging but now live-facing; forge owns the reviewed public - Gitea HTTPS ingress for the web UI, package registry, and OCI registry. Raw + Forgejo HTTPS ingress for the web UI, package registry, and OCI registry. Raw node IP HTTP access is not part of the supported forge surface. - Usage: canonical operational reference for forge, registry, runner, retention, recovery, and resource evidence. S4 owns reusable consumer templates; this @@ -125,7 +125,7 @@ The Fabric graph declarations for forge capabilities and edges live in Known starting point: -- `railiance-forge` owns Gitea Helm values, registry overlays, public HTTPS +- `railiance-forge` owns forge Helm values, registry overlays, public HTTPS ingress, operating contracts, and deploy/status entry points. - `railiance-apps` keeps app release ownership and transitional compatibility wrappers for old Gitea commands. @@ -203,7 +203,7 @@ Known starting point: ```capability type: infrastructure title: Railiance source forge operation -description: Operate the current Gitea source forge and plan future Forgejo migration/cutover as dedicated Railiance forge infrastructure. +description: Operate the current Forgejo source forge (migrated from Gitea) and plan future forge changes as dedicated Railiance forge infrastructure. keywords: [railiance, forge, gitea, forgejo, source-hosting, git] ```