Area 07 / 08 · OPS

Deployment

Phase 5 · Weeks 18–20

Ship it, keep it running, and roll it back when something breaks.

A project only counts once other people can use it. This area takes your app from a laptop to a running service: containers, CI/CD, environments, infrastructure as code, serverless and GPUs. The production half covers running it well: local models for testing, scaling, safe releases, versioning prompts and models, health checks, alerts and rollbacks.

0 of 20 used in code

01–10 · The base

Learn these first.

  • 01DockerPackage your app and everything it needs into a container that runs the same everywhere.
  • 02Docker ComposeRun several containers together (API, database, Redis) from one file.
  • 03Kubernetes BasicsPods, deployments and services: running and scaling containers on a cluster.
  • 04CI/CD PipelinesTest, build and deploy automatically on every push.
  • 05GitHub ActionsGitHub’s built-in CI/CD. Workflows are written in YAML.
  • 06Eval Gates in CIThe deploy stops if eval scores fall below your threshold.
  • 07Environment ConfigsSeparate settings and secrets for dev, staging and production.
  • 08Infrastructure as CodeDefine servers, databases and networks in code (Terraform, Pulumi) instead of clicking.
  • 09Serverless FunctionsRun code on demand without managing servers (AWS Lambda, Cloudflare Workers, Vercel).
  • 10GPU InstancesRenting GPU machines in the cloud to serve or fine-tune models.

11–20 · Production level

Come back after you have shipped something.

  • 11Ollama for Local ModelsRun open models on your own laptop with one command. Good for testing and privacy.
  • 12AutoscalingAdd or remove instances automatically as traffic goes up and down.
  • 13Load BalancingSpread requests across instances so no single one gets overloaded.
  • 14Canary ReleasesSend a small share of traffic to the new version first, then roll it out to everyone.
  • 15Feature FlagsTurn a feature on or off for some users without redeploying.
  • 16Prompt VersioningTreat prompts like code: versioned, reviewed and easy to revert.
  • 17Model VersioningPin exact model versions and record which version served each request.
  • 18Health ChecksEndpoints that tell the platform whether your app is alive and ready for traffic.
  • 19Alerts and DashboardsGet alerted on errors, latency or cost spikes, and see the trends at a glance.
  • 20RollbacksGo back to the last good version in one step.
BUILD THIS

Dockerize your RAG app and deploy it with GitHub Actions. Add an eval gate, a health check, versioned prompts and a one-step rollback.

Project guide →