Move Gitea deploy surface into forge
This commit is contained in:
parent
8b9f3b341d
commit
9ce24968cd
13 changed files with 219 additions and 78 deletions
|
|
@ -1,13 +1,12 @@
|
|||
# Gitea Package Registry
|
||||
|
||||
This is the canonical Railiance operating note for the current Gitea Python
|
||||
package registry. Compatibility pointers remain in `railiance-apps` while
|
||||
deploy-capable Gitea Helm and manifest files still live there.
|
||||
package registry. Compatibility pointers remain in `railiance-apps`;
|
||||
deploy-capable Gitea Helm and manifest files now live in this repo.
|
||||
|
||||
Gitea package support is enabled by
|
||||
`/home/worsch/railiance-apps/helm/gitea-registry-values.yaml`. That overlay is
|
||||
applied after the encrypted base values by `make gitea-deploy` and enables both
|
||||
container packages and Python packages.
|
||||
Gitea package support is enabled by `helm/gitea-registry-values.yaml`. That
|
||||
overlay is applied after the encrypted base values by `make gitea-deploy` and
|
||||
enables both container packages and Python packages.
|
||||
|
||||
## Python Packages
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue