docker-compose.yml

# Pin the compose project name so dev worktrees never collide with the
# production stack at /opt/gc. Without this, `docker compose` derives the
# project name from the worktree basename (`gc`), which matched the prod
# project on 2026-05-24 and recreated `gc-db-1` against the dev volume.
name: gc-dev

services:
  db:
    image: apache/age:release_PG16_1.6.0
    environment:
      POSTGRES_DB: ground_control
      POSTGRES_USER: ${GC_DATABASE_USER:-gc}
      POSTGRES_PASSWORD: ${GC_DATABASE_PASSWORD:?Set GC_DATABASE_PASSWORD in .env}
    ports:
      - "127.0.0.1:5432:5432"
    volumes:
      - gc-postgres-data:/var/lib/postgresql/data
    healthcheck:
      test: ["CMD-SHELL", "pg_isready -U gc -d ground_control"]
      interval: 5s
      timeout: 5s
      retries: 5

  redis:
    image: redis:7
    ports:
      - "127.0.0.1:6379:6379"
    healthcheck:
      test: ["CMD", "redis-cli", "ping"]
      interval: 5s
      timeout: 5s
      retries: 5

  backend:
    build:
      context: .
      dockerfile: backend/Dockerfile
    environment:
      GC_DATABASE_URL: jdbc:postgresql://db:5432/ground_control
      GC_DATABASE_USER: ${GC_DATABASE_USER:-gc}
      GC_DATABASE_PASSWORD: ${GC_DATABASE_PASSWORD:?Set GC_DATABASE_PASSWORD in .env}
      GC_REDIS_URL: redis://redis:6379
      GC_SERVER_PORT: "8000"
      GH_TOKEN: ${GITHUB_PERSONAL_ACCESS_TOKEN:-}
      SPRING_PROFILES_ACTIVE: dev
    ports:
      - "8000:8000"
    depends_on:
      db:
        condition: service_healthy
      redis:
        condition: service_healthy

volumes:
  gc-postgres-data: