generated from coulomb/repo-seed
7.9 KiB
7.9 KiB
Current Forge Asset Inventory
Date: 2026-06-05
This inventory covers forge-related assets that were originally visible in
/home/worsch/railiance-apps. It supports FORGE-WP-0001-T03 and the
coordinating RAILIANCE-WP-0006 extraction plan.
Canonical docs and deploy-capable Gitea files have now moved into
railiance-forge. railiance-apps keeps compatibility pointers and wrappers
while app-release ownership remains there.
Summary
| Disposition | Meaning |
|---|---|
| Move | Canonical file should move to railiance-forge. |
| Moved | Canonical file has moved to railiance-forge. |
| Copy pointer | Copy canonical content to railiance-forge, leave a short pointer in railiance-apps temporarily. |
| Leave | Keep in railiance-apps; it is S5 app-release surface. |
| Adapt | Keep local behavior, but update references after forge extraction. |
| Supersede | Historical or transitional content should be replaced by new forge-owned docs/workplans. |
Move To railiance-forge
| Asset | Current role | Target disposition | Notes |
|---|---|---|---|
helm/gitea-values.sops.yaml |
SOPS-encrypted Gitea Helm values. | Moved | Now railiance-forge/helm/gitea-values.sops.yaml; moved without decrypting. |
helm/gitea-registry-values.yaml |
Non-secret overlay enabling Gitea package/container registry behavior. | Moved | Now railiance-forge/helm/gitea-registry-values.yaml. |
manifests/gitea-ingress.yaml |
Registry-facing Gitea ingress for /v2. |
Moved | Now railiance-forge/manifests/gitea-ingress.yaml; labels left unchanged until next reviewed deploy. |
releases/gitea/values.yaml |
Legacy/plain Gitea release values reference. | Moved | Now railiance-forge/releases/gitea/values.yaml; review before using as active deploy input. |
Makefile variables GITEA_* |
Gitea release/chart/value/ingress defaults. | Moved | Forge owns canonical variables; apps keeps only release/name compatibility variables. |
make gitea-deploy |
Deploy/upgrade current Gitea release. | Moved | Forge owns target; apps delegates during compatibility window. |
make gitea-ingress-deploy |
Apply Gitea registry ingress. | Moved | Forge owns target; apps delegates during compatibility window. |
make gitea-status |
Check Gitea pod/service/ingress and gitea-db status. |
Moved | Forge owns target; apps delegates during compatibility window. |
Copy With Compatibility Pointer
| Asset | Current role | Target disposition | Notes |
|---|---|---|---|
docs/gitea-container-registry.md |
Canonical operator recipe for container registry host, auth, pull secrets, storage note. | Moved | Forge doc is canonical; app-side file is a compatibility pointer. |
docs/gitea-package-registry.md |
Python package registry publishing/install recipe and issue-core handoff. |
Moved | Forge doc is canonical; app-side file is a compatibility pointer. |
workplans/RAIL-AP-WP-0001-gitea-container-registry.md |
Historical implementation evidence for enabling Gitea registry in S5. | Copy pointer or archive | Keep historical record in S5, but create forge follow-up for storage/retention/restore posture. |
workplans/RAILIANCE-WP-0006-railiance-forge-extraction.md |
Cross-repo coordination plan. | Leave plus pointer | Remains in railiance-apps as extraction coordinator; forge work proceeds in FORGE-WP-*. |
Leave In railiance-apps
| Asset | Current role | Target disposition | Notes |
|---|---|---|---|
.gitea/workflows/manifest-server-dry-run.yaml |
S5 manifest dry-run workflow for app charts/manifests. | Leave | Runner substrate belongs in forge; this app-release check remains S5. |
make k8s-server-dry-run |
Server-side dry-run for S5 charts/manifests. | Leave | Document runner/cluster prerequisites in forge, but keep app release check here. |
tools/k8s-server-dry-run.sh |
Implements S5 dry-run. | Leave | Consumes runner/cluster access; does not operate forge runtime. |
charts/vergabe-teilnahme/** |
S5 app chart. | Leave | Application release ownership. |
helm/vergabe-teilnahme-values.yaml |
S5 app values, including registry image reference. | Leave | Consumes forge registry; does not own registry. |
manifests/vergabe-teilnahme-ingress.yaml |
S5 app ingress. | Leave | Application endpoint ownership. |
docs/vergabe-teilnahme.md |
S5 app runbook. | Leave | Update links to point at forge-owned registry docs after migration. |
docs/django-on-railiance.md |
Framework-specific S5 app recipe. | Leave | Should reference forge registry capabilities as upstream infrastructure. |
docs/operator-recipes.md |
S5 operator recipes. | Leave | Keep only app-release recipes here. |
docs/operator-setup.md |
S5 operator setup. | Leave | May need forge cross-link for registry credentials and runner expectations. |
tools/build-database-url-secret.sh |
App DB secret helper. | Leave | S5 app data/secret consumer behavior. |
tools/smoke-service.sh |
App smoke helper. | Leave | S5 verification. |
make apps-pg-status |
Checks shared app database cluster. | Leave or move to platform later | Not forge; keep while S5 needs consumer readiness evidence. |
make vergabe-* targets |
App release operations. | Leave | S5 app surface. |
Adapt In Place
| Asset | Current role | Target disposition | Notes |
|---|---|---|---|
SCOPE.md |
Currently lists Gitea as S5-owned workload. | Adapt | After migration, describe forge as upstream release infrastructure. |
INTENT.md |
Mentions Gitea/current forge as S5 workload/learning surface. | Adapt | Keep S5 intent but remove long-term forge ownership language. |
AGENTS.md |
Repo identity still says application Helm releases, Gitea, coulomb services. | Adapt | Update after Gitea files move. Also update task status examples to State Hub canon. |
Makefile SOPS_SENTINEL |
check-sops validates the forge-owned Gitea SOPS sentinel for compatibility. |
Adapted | Apps points at /home/worsch/railiance-forge/helm/gitea-values.sops.yaml. |
tools/check-sops.sh |
Generic SOPS sentinel check. | Leave/adapt | Useful beyond forge, but current default must change after move. |
.custodian-brief.md |
Generated State Hub brief. | Generated | Do not edit manually; consistency sync updates it. |
Supersede Or Re-home Planning Content
| Asset | Current role | Target disposition | Notes |
|---|---|---|---|
RAILIANCE-WP-0005-T04 |
App data backup/restore handoffs includes Gitea package blobs. | Split | App DB handoff stays S5; Gitea package blob durability moves to forge. |
RAILIANCE-WP-0005-T06 |
Gitea package registry storage and retention posture. | Re-home | Should become forge-owned follow-up, likely under FORGE-WP-*. |
railiance-apps-WP-0004 I03 |
PyPI issue-core blocker references Gitea package registry. | Adapt | Source/package publication remains source repo; forge owns registry endpoint and credentials posture. |
railiance-apps-WP-0002 registry references |
Historical app deployment evidence. | Leave/adapt | Keep as app deployment history; cross-link to forge docs for current registry operation. |
First Safe Move Candidate
The first migration avoided live service changes and moved documentation before deployment configuration:
- Copy
docs/gitea-container-registry.mdanddocs/gitea-package-registry.mdintorailiance-forge/docs/. - Replace the originals in
railiance-appswith short compatibility pointers. - Add a
railiance-forge/Makefilewith read-only/status targets first. - Move deploy-capable Gitea targets only after the operator path is reviewed.
- Keep app-side compatibility wrappers until operators have switched.
This gives operators a canonical forge home while keeping current S5 app runbooks discoverable.
Remote Creation Note
coulomb/railiance-forge now exists and the local repo is pushed to
gitea-remote:coulomb/railiance-forge.git.