Docker And Container Strategy

Sprint 23 adds a conservative container strategy for future staging:

• Dockerfile.web builds and runs @submicron/web on port 3000.
• Dockerfile.docs builds and runs @submicron/docs on port 3001.
• docker-compose.staging.yml shows a staging layout using an untracked .env.staging.
• .dockerignore excludes local env files, private imports, review output, caches, and git metadata.

Build

docker build -f Dockerfile.web -t submicron-web:staging .
docker build -f Dockerfile.docs -t submicron-docs:staging .

Run

docker compose -f docker-compose.staging.yml up --build

Staging should normally sit behind a reverse proxy that terminates HTTPS and forwards to the web container. Do not put real secrets in Dockerfiles or committed Compose files.

Ports

• Web app: 3000
• Docs app: 3001

Use a process manager or container orchestrator that restarts failed containers and preserves logs. Production deployment remains out of scope for Sprint 23.