B. Blue Green a software delivery tutorial
Vol. I § Zero-downtime series § A series for junior developers
Prerequisite map

Zero-downtime delivery

A Titik Terang lab series for junior developers. Two slots, one proxy, one playbook, and a switch that moves only after a health check.

1Why a restart is downtime2Two slots, one of them live3Dockerfile.base and Dockerfile.app4A private registry and tag rules5Caddy holds the public port6The playbook only touches the idle slot7The health check is the gate8GitHub Actions runs the playbook9Vault Agent writes secrets into memory10Rollback moves the switch back
not startedreadcurrentrequiredrecommended
Chapters 10
  1. 01 Why a restart is downtime downtime
  2. 02 Two slots, one of them live slots
  3. 03 Dockerfile.base and Dockerfile.app docker
  4. 04 A private registry and tag rules registry
  5. 05 Caddy holds the public port caddy
  6. 06 The playbook only touches the idle slot ansible
  7. 07 The health check is the gate health-check
  8. 08 GitHub Actions runs the playbook ci
  9. 09 Vault Agent writes secrets into memory vault
  10. 10 Rollback moves the switch back rollback