feat(gitea): enable the package registry
The backend template is moving its messaging and gRPC libraries into separate repositories and will consume them as Maven versions from Gitea Packages. [packages] ENABLED=false and repo.packages in DISABLED_REPO_UNITS make the registry unavailable. Turn on [packages] and leave DISABLED_REPO_UNITS as an explicit empty value. The chart init container runs `gitea config edit-ini --apply-env` against the app.ini on the data volume, so a removed key would keep the old disabled list; an empty value overwrites it. SSH and LFS stay off. This ships with the Actions change in the same rollout, so Gitea restarts once. Risk: packages are stored under /data/packages on the root SSD local PV. The 50Gi PVC size is not enforced by a local PV; the real bound is free space on the host root disk, shared with the host and the CI runner. No per-owner size limit is set yet. Verification: render-phase1.sh invariants pass; kubectl diff against live shows only the inline-config keys actions, packages, repository and the Deployment checksum/config annotation. Refs: Gitea 1.27 config cheat sheet [packages], usage/packages
This commit is contained in:
@@ -95,14 +95,16 @@ gitea:
|
||||
queue:
|
||||
TYPE: level
|
||||
|
||||
# Actions is on at the server level. Repositories created while the unit
|
||||
# was disabled keep has_actions=false until an owner turns it on.
|
||||
# Actions and Packages are on at the server level. Repositories created
|
||||
# while a unit was disabled keep it off until an owner turns it on.
|
||||
actions:
|
||||
ENABLED: true
|
||||
packages:
|
||||
ENABLED: false
|
||||
ENABLED: true
|
||||
# Kept as an explicit empty value: app.ini on the data volume persists, so
|
||||
# dropping the key would leave the previous disabled list in place.
|
||||
repository:
|
||||
DISABLED_REPO_UNITS: "repo.packages"
|
||||
DISABLED_REPO_UNITS: ""
|
||||
|
||||
additionalConfigFromEnvs:
|
||||
- name: GITEA__DATABASE__USER
|
||||
|
||||
Reference in New Issue
Block a user