ashwin/nxtgauge-gitops
0
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
nxtgauge-gitops/apps/traceworks2026
History
sync-test d5bce052ac
All checks were successful
sync-to-github / sync (push) Successful in 16s
Details
feat(traceworks2026): add animated journey phases to learn page
2026-08-04 07:40:26 +05:30
..
base feat(traceworks2026): add learn.traceworks.in ingress and deploy updated frontend image 2026-08-04 04:16:25 +05:30
overlays/prod feat(traceworks2026): add animated journey phases to learn page 2026-08-04 07:40:26 +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.