The free course ends with a running app and an honest gap: cargo run on your laptop is not a website. This course closes that gap the way the port opened it — one deliberate layer at a time, with you performing every step.

By lesson 9 the pet store lives on a domain you own, behind automatic TLS, its database continuously replicated off the machine, and shipping a bad release costs you one command to undo. The deployment artifact this course produces is a 7.7 megabyte container image that idles at about 1.3 megabytes of memory — numbers your old app server couldn’t say with a straight face.

What the nine lessons build

Each lesson is a working checkpoint, tagged deploy-01 through deploy-09 in the same companion repo the free course used — public code, because what you’re buying is the guided path, the reasons behind every line, and the guarantee.

  1. Config crosses the boundary: two env vars, defaults preserving dev
  2. The two-stage Dockerfile: toolchain in, one file out
  3. The endgame image: static musl build, FROM scratch, 7.7 MB
  4. A registry and a build script: immutable tags plus :latest
  5. Compose, an external volume, and a binary that healthchecks itself
  6. The server: bare VPS to running stack, over SSH
  7. Caddy: TLS as three lines of config
  8. Litestream: continuous replication, and a restore you perform
  9. Updates and rollbacks: redeploy with a smaller number

Two lessons carry war stories found while building this course for real: the scratch image has no curl, so the binary learns to probe itself — and lesson 8’s restore drill fails the first time you do it naively, because the restored file belongs to root and your app doesn’t run as root. You’ll hit both on purpose, with the fix and the reasoning.

Who this is for

You finished the port (or you have a Rust binary of your own) and deploying it is the part you’ve never owned end to end. In the WAR-file world an ops team stood between your build and the internet; this course is that team’s job description, compressed to an evening and a half of focused work.

The guarantee is the same Power Guarantee as every paid course: finish the lessons, do the challenges, and if your deployment doesn’t serve, I’ll debug it with you — double your money back if we can’t fix it together.