Chapter 16: Capstone — Ship It End-to-End

16.2 Scope — what "done" means

By Ravindra Bagale · Last updated: 1 October 2026

In scope (pick tools you already practised):

1. Small API or static+API hello that serves /health and a tiny /badge (or equivalent).
2. Dockerfile that builds a runnable image.
3. docker-compose.yml for local API (+ optional DB/redis) with a volume lesson remembered.
4. GitHub Actions workflow: PR tests; main builds and pushes an image tagged with git SHA (GHCR or Docker Hub — your choice).
5. One deploy path (choose A or B — do not half-do both): - A: SSH/Ansible (or Actions SSH step) pulls/runs the tagged image on one lab VM. - B: kind local cluster with Deployment + Service + port-forward (Chapter 15).
6. README runbook sections listed below.
7. Monitoring/logging ping: at least one host metric dashboard note or one log query note from Chapters 13–14 (does not need production polish).
8. Cleanup: stop compose, destroy terraform leftovers if any, kind delete if used, stop idle VMs.

Out of scope: full VPC redesign, real payment gateways, real customer data, invented AWS prices, PDF uploads to the website.