feat(binjovi-flux-deployer): deploy from a mirror source, roll back through Forgejo main #367
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/flux-deployer-mirror-source"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What
binjovi-flux-deployv12 gains--mirror-url(exclusive with the retired--codeberg-repo, kept for the transition): Forgejomainis the deploy pointer, a Forgejo push mirror carries it to the off-cluster copy Flux reads, and the deployer only observes that copy (30 reads, 3 s apart; refuses a diverged mirror). Rollback moves Forgejomainback with--force-with-leaseon the released revision, the token handed to git through a credential helper (never in argv), then waits for the mirror and Flux to follow.Verified
scripts/check-binjovi-flux-deployer.sh: exclusive flags, URL validation, mirror observation on the ninth read, bounded failure, and a stubbed rollback whose push carries the lease and lands oncode.sean.farm, with the mirror and Flux followed to the old revision. Green.Follow-ups in the same sitting: binjovi (
mirror_urlflux targets, agents mount the Forgejo token, Dockerfile pin v12), binjovi-plans (mirror_url), seanfarm (Flux source →code.packet.town).https://claude.ai/code/session_01XdBRc9CHgFhAxCyHbdVtt6