B. Blue Green a software delivery tutorial
Vol. I § Zero-downtime series § A series for junior developers
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.

Slot playground · pipeline
gitbuildregistryplaybook
A git push starts the path.
  1. A git push starts the path.
  2. The base image, then the app image, is built.
  3. The image is pushed to registry.titikterang.local:5000.
  4. CI runs ansible-playbook against the idle slot.

Quick recap

  • vX.Y.Z for releases, vX.Y.Z-dev for candidates; the playbook refuses to mix them.
  • latest cannot be rolled back; explicit tags can.
  • The registry stores your release history — that is part of the rollback strategy, not just storage.

Reader notes

Chapter discussion appears once Giscus is connected to the site repository.