coulomb/the-custodian
Archived
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

railiance-bootstrap to railiance-cluster rename cleanup

Browse Source
This commit is contained in:
Bernd Worsch
2026-05-03 16:30:07 +02:00
parent 190704a4eb
commit 85bf0bc180
10 changed files with 17 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
workplans/CUST-WP-0011-state-hub-threephoenix-migration.md
View File

@@ -194,8 +194,14 @@ local image `state-hub:local` successfully:
current database when run locally with host networking. Verified Alembic is
available in-image and reports current revision `r5m6n7o8p9q0 (head)`.
Remaining: choose and authenticate a registry target so the image can be
tagged, pushed, and pulled from railiance01.
Progress 2026-05-03: registry target decision resolved to the self-hosted
Gitea registry. A local SSH tunnel to the NodePort can reach Gitea, but Docker
login/push still receives HTTP 404 from `/v2/`. Runtime inspection shows the
live Gitea `app.ini` has no `[packages]` section, so package registry
enablement/routing must be applied before publishing `state-hub:local`.
Remaining: enable the Gitea package/container registry, then tag, push, and
pull the image from railiance01.
---