docker-compose.yaml

services:
  # Plain Postgres + pgvector, not the full Supabase platform image.
  #
  # This was originally `supabase/postgres:15.6.1.143` (the full Supabase
  # platform image, which bundles Auth/Storage/Realtime and expects its own
  # migration bootstrapping — a `supabase_admin` role, JWT secrets, etc.).
  # This project never touches any of that: src/utils/db.py and
  # scripts/init_db.py only ever run plain psycopg2 SQL (CREATE EXTENSION
  # vector, a document_chunks table, a match_chunks() function). Against a
  # real Docker/colima run, the supabase/postgres image's own
  # docker-entrypoint migration script failed
  # ("password authentication failed for user supabase_admin" — that role
  # is never created because the platform bootstrap env vars this image
  # expects were never set) and the container exited immediately. Swapping
  # to the official, minimal pgvector image is the actual fix, not a
  # workaround — see README's "Local Postgres image" note. Table name,
  # port, and connection details are unchanged, so nothing else in the repo
  # needed to change.
  supabase-db:
    image: pgvector/pgvector:pg15
    ports:
      - "54322:5432"
    environment:
      POSTGRES_USER: postgres
      POSTGRES_PASSWORD: postgres
      POSTGRES_DB: postgres
    volumes:
      - supabase_data:/var/lib/postgresql/data
    healthcheck:
      test: ["CMD-SHELL", "pg_isready -U postgres"]
      interval: 5s
      timeout: 5s
      retries: 5

volumes:
  supabase_data: