Files
portfolio/docker-compose.dev.minimal.yml
denshooter a5449d2adb
All checks were successful
Dev Deployment (Zero Downtime) / deploy-dev (push) Successful in 16m12s
fix: use external network for dev compose to avoid label conflicts
The portfolio_dev network was created manually by the pipeline, causing
docker-compose to fail with label mismatch errors. Now:
- Network is marked as external in compose (compose doesn't try to own it)
- Network creation moved before compose up in the pipeline
- Redundant network check later in pipeline removed

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-18 11:37:35 +01:00

44 lines
1.1 KiB
YAML

services:
# PostgreSQL Database
postgres:
image: postgres:16-alpine
container_name: portfolio_postgres_dev
environment:
POSTGRES_DB: portfolio_dev
POSTGRES_USER: portfolio_user
POSTGRES_PASSWORD: portfolio_dev_pass
# POSTGRES_HOST_AUTH_METHOD removed - using default password authentication (more secure)
volumes:
- postgres_dev_data:/var/lib/postgresql/data
# init-db.sql mount removed - database is initialized via POSTGRES_DB/POSTGRES_USER
# Additional grants can be done via Prisma migrations if needed
networks:
- portfolio_dev
healthcheck:
test: ["CMD-SHELL", "pg_isready -U portfolio_user -d portfolio_dev"]
interval: 10s
timeout: 5s
retries: 5
# Redis for caching
redis:
image: redis:7-alpine
container_name: portfolio_redis_dev
volumes:
- redis_dev_data:/data
networks:
- portfolio_dev
healthcheck:
test: ["CMD", "redis-cli", "ping"]
interval: 10s
timeout: 5s
retries: 5
networks:
portfolio_dev:
external: true
volumes:
postgres_dev_data:
redis_dev_data: