promptdojo_promptdojo_promptdojo_promptdojo_promptdojo_promptdojo_promptdojo_promptdojo_promptdojo_promptdojo_promptdojo_

Docker runtime and config shape — step 7 of 7

ch 46 · model serving, ci/cd, and mlopsch 46 · model serving, ci/cd, and mlopsch 46 · model serving, ci/cd, and mlopsch 46 · model serving, ci/cd, and mlopsch 46 · model serving, ci/cd, and mlopsch 46 · model serving, ci/cd, and mlopsch 46 · model serving, ci/cd, and mlopsch 46 · model serving, ci/cd, and mlopsch 46 · model serving, ci/cd, and mlopsch 46 · model serving, ci/cd, and mlopsch 46 · model serving, ci/cd, and mlops7/7
Checkpoint

One last thing before we move on. pass this to mark the lesson done, or skip and keep moving. hop to the next when you're ready.

Partition the deployment. Each item belongs in exactly one home: "image" (frozen runtime), "runtime env" (differs per environment), "secret manager" (credentials, injected), or "registry at startup" (the model — so deploying a new model never rebuilds the runtime). Print each as f"{name:<25} -> {home}" in the given order, then a sorted summary dict of counts. This partition IS the lesson: what's frozen, what varies, what's secret, what's versioned separately.

full-screen editor opens — close anytime to keep reading.

open the editor to run it.