coulomb/railiance-forge
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs: name Forgejo as the current forge, keep gitea identifiers for compatibility
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details

Browse source 
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
This commit is contained in:
tegwick 2026-10-18 02:36:09 +02:00
parent d55d4dbd26
commit fa5d1af0a1
7 changed files with 32 additions and 26 deletions
Download patch file Download diff file Expand all files Collapse all files

22
SCOPE.md
View file

@ -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]
```