Chapter 16: Capstone — Ship It End-to-End
16.1 Why a capstone — one story you can tell
Interviews rarely ask you to recite every flag. They ask: tell me about something you shipped.
This chapter stitches Chapters 1–15 into one real-world-style path — an Instagram-style profile badge API (or a Netflix-style tiny update service): code → image → pipeline → running environment → health check → rollback note → cleanup.
Optional flavour: pretend you are handing the same lab to an Infosys-style client operations team — your README must be clear enough that someone else can run it.
You will not build a huge product empire. You will build a boring, complete lab story with evidence (commands, screenshots in your own repo, checklist).
| Incomplete portfolio | Capstone-complete |
|---|---|
| Dockerfile only | Dockerfile + Compose + workflow + runbook |
| "It ran once" | Health check + rollback tag documented |
| Secrets in Git history | .gitignore + placeholders only |
| Leftover cloud bill surprise | Destroy/delete checklist done |
Ravindra Bagale's Tip
Capstone fail hote jevha deploy nantar health check skip. Curl /health — bilkul visru nako. Dhyan rakho!