docker-compose.yml

# ─────────────────────────────────────────────────────────────────────────────
# Local development — connects directly to:
#   - Linode Postgres (via VPN)
#   - Real S3 Bronze bucket (via your AWS credentials)
#
# No LocalStack. No simulation.
# The same container image runs locally and in AWS Batch — zero code difference.
#
# Build context is the repo root so the Dockerfiles can COPY shared code from
# containers/_shared/ alongside their object-specific code.
#
# Usage:
#   docker compose build parcel-extract
#   docker compose run --rm parcel-extract
#   docker compose build verse-extract
#   docker compose run --rm verse-extract
# ─────────────────────────────────────────────────────────────────────────────

services:

  parcel-extract:
    build:
      context: .
      dockerfile: containers/parcel-extract/Dockerfile
    env_file:
      - ./dev/.env.local          # credentials — never committed
    # All other env vars are in .env.local
    # In AWS Batch, these come from the job definition + Secrets Manager

  verse-extract:
    build:
      context: .
      dockerfile: containers/verse-extract/Dockerfile
    env_file:
      - ./dev/.env.local
    volumes:
      # Mount host config/ over the baked-in copy so local dev can iterate on
      # the YAML (query, partition_cols) without rebuilding the image.
      # In AWS Batch, the baked-in copy from the Dockerfile is used.
      - ./config:/app/config:ro