Step 9: Containerize & Ship

Generate a production Dockerfile and deploy to your hosting target.

What you're doing in this step

Turn 'works on my machine' into a reproducible image you can roll back in one command.

Recommended prompts

Use one of these to do the work in your IDE

Open the template to read it in full. Click Copy prompt to grab it (with your stack values pre-filled where they apply) — then paste into Claude Code, Cursor, or wherever you build.

Primary recommendation 10 min

Production Dockerfile Generator

Generate a multi-stage, security-hardened Dockerfile with minimal image size.

docker

View template

Template· Template 15 min

GitHub Actions CI/CD Pipeline

Generate a GitHub Actions workflow for build, test, lint, and deploy with proper caching and security.

Use this when: You also need a CI pipeline that builds the image and runs tests on PRs

github-actions

View template

When you're done

Verify these in your own work before moving on

This is a checklist for you to mentally tick off in your repo and IDE — the site doesn't track it, you do.

Multi-stage Dockerfile, non-root user, pinned base image
Image builds clean with no warnings
App boots in container locally
Deployed to staging and smoke-tested
Production deploy gated on staging green

Common pitfalls

What goes wrong at this step

Running as root in the container — easy security gain by switching to a non-root user
`COPY . .` instead of explicit paths — bloats the image and leaks secrets

← Previous step

Use one of these to do the work in your IDE

Production Dockerfile Generator

GitHub Actions CI/CD Pipeline

Verify these in your own work before moving on

What goes wrong at this step

Command Palette