coulomb/railiance-apps
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

feat(vergabe): deploy from Forgejo OCI registry only
Some checks are pending
CI Smoke / host-smoke (push) Waiting to run
Details
CI Smoke / container-smoke (push) Waiting to run
Details

Browse source 
Switch helm values and Makefile image gates to forgejo.coulomb.social;
retire gitea.coulomb.social for vergabe-teilnahme production pulls.
This commit is contained in:
tegwick 2026-07-12 00:32:32 +02:00
parent 4c32a65edd
commit e9f406da2a
4 changed files with 33 additions and 19 deletions
Download patch file Download diff file Expand all files Collapse all files

14
docs/vergabe-teilnahme.md
View file

@ -68,13 +68,13 @@ make vergabe-superuser # interactive createsuperuser
## Promoting a new image tag
1. Build + push from the `vergabe-teilnahme` repo using the portable package
path: `issue-core` resolves from the Gitea PyPI registry, not from a sibling
checkout.
2. Update `image.tag` in `helm/vergabe-teilnahme-values.yaml` to the
new git SHA.
3. `make vergabe-deploy` — Helm rolls a new ReplicaSet with
zero-downtime (`maxSurge: 1, maxUnavailable: 0`).
1. Build + push via Forgejo Actions (`.forgejo/workflows/image.yaml` on push to
`main`) or locally:
`docker login forgejo.coulomb.social` then build/push
`forgejo.coulomb.social/coulomb/vergabe-teilnahme:<sha>`.
2. Set `VERGABE_IMAGE_TAG=<sha> make vergabe-deploy` (values default repository
is `forgejo.coulomb.social/coulomb/vergabe-teilnahme`).
3. Helm rolls a new ReplicaSet with zero-downtime (`maxSurge: 1, maxUnavailable: 0`).
4. Verify via `make vergabe-status` and an HTTPS probe.
5. If migrations are needed, run `make vergabe-migrate` after the
rollout completes.