ashwin/nxtgauge-gitops
0
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
nxtgauge-gitops/apps/traceworks2026
History
Rimuru 1a9fae467b traceworks2026: deploy mobile-fix release 
Frontend: 20260708200848-f50217d32a9c (mobile CSS pass, hamburger menu)
API:      20260708200914-f50217d32a9c

Previous image (19700101000000-000000000000) was a placeholder.
Flux couldn't reconcile because build workflow tags were short SHAs
not matching the YYYYMMDDhhmmss-GITSHORT12 regex policy.
2026-07-09 01:41:04 +05:30
..
base Add Traceworks Flux image automation 2026-07-05 23:04:54 +05:30
overlays/prod traceworks2026: deploy mobile-fix release 2026-07-09 01:41:04 +05:30
README.md Add Traceworks Flux image automation 2026-07-05 23:04:54 +05:30

README.md

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.