~14 min · compose, operations
Some services should only start when needed: a DB GUI, a mail catcher, a debug dashboard. Tag them with a profile and Compose ignores them by default.
Compose auto-merges compose.yaml with compose.override.yaml if the override exists. Convention: base file is prod-shaped, override file is dev-tweaks (bind mounts, --reload, debug ports). Production uses -f compose.yaml -f compose.prod.yaml instead.
services:
api:
build: ./api
db:
image: postgres:16
environment:
POSTGRES_PASSWORD: secret
# Optional services
adminer:
image: adminer
profiles: [debug]
ports: ["8080:8080"]
mailhog:
image: mailhog/mailhog
profiles: [debug]
ports: ["1025:1025", "8025:8025"]# compose.override.yaml — auto-loaded in dev
services:
api:
volumes:
- ./api:/app
environment:
APP_ENV: development
command: uvicorn main:app --reload --host 0.0.0.0
# Use:
# docker compose up -d ← merges base + override (dev)
# docker compose --profile debug up -d ← also starts debug services
# docker compose -f compose.yaml -f compose.prod.yaml up -d ← proddebug profile to one of your compose stacks with adminer (or pgadmin) and mailhog. Verify they only start with --profile debug. Then add a compose.override.yaml that bind-mounts your source for hot-reload. Switch between dev and prod with -f and verify the difference.No comments yet — be the first.