17 lines
630 B
Markdown
17 lines
630 B
Markdown
# Traceworks2026 GitOps
|
|
|
|
This app is deployed from `apps/traceworks2026/overlays/prod`.
|
|
|
|
Flux image automation watches these Forgejo registry images:
|
|
|
|
- `ci.nxtgauge.com/admin/traceworks2026-frontend`
|
|
- `ci.nxtgauge.com/admin/traceworks2026-api`
|
|
|
|
Expected CI flow:
|
|
|
|
1. GitHub mirrors the app repo to Forgejo.
|
|
2. Forgejo Actions builds and pushes timestamped image tags.
|
|
3. Flux updates `overlays/prod/release-patch.yaml` to the newest tags.
|
|
4. Flux applies the updated manifests to the cluster.
|
|
|
|
Before this works in-cluster, create a `forgejo-regcred` secret in the `flux-system` namespace so Flux can read the private registry.
|