Deployment

Infrastructure Overview

All services run as Docker containers on a Hetzner Cloud VPS behind an nginx reverse proxy with Let's Encrypt SSL.

Docker Images

Images are built and pushed to GitHub Container Registry (GHCR):

All images use multi-stage builds:

1. Pruner — turbo prune isolates the workspace
2. Installer — install deps and build
3. Runner — minimal production image

CI/CD Pipeline

CI (ci.yml)

Triggered on push to main and pull requests:

1. Lint, Typecheck & Build — runs on all PRs and pushes
2. Build & Push Docker Images — only on main push, pushes to GHCR
3. Docker Build Validation — on PRs, validates Docker builds without pushing

Deploy (deploy.yml)

Manual dispatch workflow:

1. Generates .env file on VPS from GitHub secrets
2. Pulls Docker images from GHCR
3. Restarts services with docker compose up -d
4. Runs health checks against production URLs

Production Docker Compose

The production stack (docker/docker-compose.prod.yml) includes:

• cpi-postgres — TimescaleDB with persistent volume
• cpi-redis — Redis with password auth
• cpi-mosquitto — MQTT broker with TLS certificates
• cpi-api — NestJS API (depends on postgres + redis + mosquitto)
• cpi-admin — React SPA served by nginx
• cpi-docs — Next.js documentation site

Database Migrations

Migrations run automatically on API container startup (migrationsRun: true). No manual migration step needed during deployment.

Migration files are in apps/api/src/database/migrations/.

Environment Variables

Key environment variables for production:

Health Checks

Local Development

pnpm docker:up      # Start infrastructure
pnpm dev:apps        # Start API + Admin
pnpm dev:docs        # Start documentation site

See Getting Started for full setup instructions.