nxtgauge-gitops/apps/traceworks2026
sync-test 33049d5c74
All checks were successful
sync-to-github / sync (push) Successful in 14s
docs(traceworks2026): update api-secret template for ZeptoMail + PayU
Reflects the real secret keys now used in traceworks-api-env (ZeptoMail SMTP
replaces Resend, PayU credentials, GST seller details) -- no real values,
placeholders only.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-08-04 21:40:03 +05:30
..
base docs(traceworks2026): update api-secret template for ZeptoMail + PayU 2026-08-04 21:40:03 +05:30
overlays/prod chore(gitops): update nxtgauge app images 2026-08-04 02:14:09 +00:00
README.md Add Traceworks Flux image automation 2026-07-05 23:04:54 +05:30

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.