dev_arc_aws/.forgejo/workflows
Samuel James bddf891c0a
All checks were successful
Build & Push Images / build (push) Successful in 38s
CI / validate (push) Successful in 1m11s
Build & Push Images / deploy (push) Successful in 23s
Auto-deploy to racknerd2 after a successful build
Add a `deploy` job to build.yml that needs `build`, so every push to main
builds + pushes the images and then deploys them to racknerd2 over the
mesh, pinned to the built commit's SHA, with an /api/health gate. Fully
hands-off.

The standalone deploy.yml stays as a manual workflow_dispatch for
deploying/rolling back to an arbitrary tag without rebuilding.

deploy/README.md updated to document the auto-deploy flow.

Co-authored-by: Samuel James <ssamjame@amazon.com>
Co-authored-by: Kiro <noreply@kiro.dev>
2026-06-25 11:34:27 -04:00
..
build.yml Auto-deploy to racknerd2 after a successful build 2026-06-25 11:34:27 -04:00
ci.yml Add Forgejo Actions CI, remove GitHub Actions (#1) 2026-06-23 22:52:35 +00:00
deploy.yml Add Forgejo Actions build + deploy pipeline (registry -> racknerd2) 2026-06-25 10:04:59 -04:00