# Compose Stacks This folder is for the self-contained local stack (self-signed TLS) and Traefik assets. Remote environments use the shared compose files in `infra/base` together with `infra/scripts/deploy.sh`. ## Local development (self-signed TLS) - Copy envs: `cp infra/compose/env.example infra/compose/.env` then set passwords/secrets and the dev domain (defaults to `local.lan`). - Host aliases: add the domain to `/etc/hosts` (e.g. `127.0.0.1 auth.local.lan api.local.lan grafana.local.lan vault.local.lan minio.local.lan`). - Networks: `./infra/scripts/setup-networks.sh` (creates `apa-frontend` and `apa-backend` used everywhere). - Run: `cd infra/compose && docker compose --env-file .env -f docker-compose.local.yml up -d`. - Stop: `docker compose --env-file .env -f docker-compose.local.yml down`. - TLS: Traefik mounts `infra/compose/traefik/certs/local.{crt,key}`. Regenerate if needed with `openssl req -x509 -newkey rsa:2048 -nodes -keyout infra/compose/traefik/certs/local.key -out infra/compose/traefik/certs/local.crt -days 365 -subj "/CN=*.local.lan"`. ## Cloud / remote (Let’s Encrypt) - Config lives in `infra/base` with env files in `infra/environments/{development,production}/.env`. - Create the same docker networks on the host (`./infra/scripts/setup-networks.sh`) so Traefik and services share `apa-frontend` / `apa-backend`. - Deploy on the server: `./infra/scripts/deploy.sh all` (or `infrastructure`, `monitoring`, `services`). - Certificates: Traefik uses DNS-01 via GoDaddy from the provider env in `infra/base/traefik/config` (make sure `DOMAIN`, ACME email, and provider creds are set in the env file). ## Files of note - `docker-compose.local.yml` – full local stack. - `traefik/traefik.local.yml` and `traefik/traefik-dynamic.local.yml` – static/dynamic Traefik config for local. - `traefik/certs/` – self-signed certs used by the local proxy. - `env.example` – defaults for local `.env`.