Zero-downtime delivery · 4 / 10 ·
A private registry and tag rules
A private registry holds images you never send to the public internet. The lab uses registry.titikterang.local:5000. Everything you ever released lives there, ready to be pulled again — including when you need a rollback.
Two tag shapes
- Live release:
v1.2.3 - Candidate:
v1.2.4-dev
The playbook refuses to push a candidate onto a live production slot. The rule is simple: a tag without a -dev suffix is a release that already passed its tests.
- A git push starts the path.
- The base image, then the app image, is built.
- The image is pushed to registry.titikterang.local:5000.
- CI runs ansible-playbook against the idle slot.
Quick recap
vX.Y.Zfor releases,vX.Y.Z-devfor candidates; the playbook refuses to mix them.latestcannot be rolled back; explicit tags can.- The registry stores your release history — that is part of the rollback strategy, not just storage.