Delegate Gitea operations to forge
This commit is contained in:
parent
421c09e902
commit
a715be6d28
7 changed files with 46 additions and 58 deletions
|
|
@ -6,8 +6,8 @@ Canonical registry operating guidance now lives in:
|
|||
/home/worsch/railiance-forge/docs/gitea-container-registry.md
|
||||
```
|
||||
|
||||
This compatibility pointer remains in `railiance-apps` while deploy-capable
|
||||
Gitea Helm, SOPS, and manifest files are still migrating under
|
||||
This compatibility pointer remains in `railiance-apps` after deploy-capable
|
||||
Gitea Helm, SOPS, and manifest files moved to `railiance-forge` under
|
||||
`RAILIANCE-WP-0006-T03`.
|
||||
|
||||
Use `railiance-forge` for registry endpoints, package-token handling, smoke
|
||||
|
|
|
|||
|
|
@ -6,8 +6,8 @@ Canonical package-registry operating guidance now lives in:
|
|||
/home/worsch/railiance-forge/docs/gitea-package-registry.md
|
||||
```
|
||||
|
||||
This compatibility pointer remains in `railiance-apps` while deploy-capable
|
||||
Gitea Helm, SOPS, and manifest files are still migrating under
|
||||
This compatibility pointer remains in `railiance-apps` after deploy-capable
|
||||
Gitea Helm, SOPS, and manifest files moved to `railiance-forge` under
|
||||
`RAILIANCE-WP-0006-T03`.
|
||||
|
||||
Use `railiance-forge` for the Gitea PyPI endpoint, package-token handling,
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue