# docker-compose.yml — PgBouncer in front of timescale_db.
# ─────────────────────────────────────────────────────────────────────────────
# Deploy:
#   1. Apply auth_setup.sql to the DB as postgres (creates pgbouncer_auth + lookup fn).
#   2. Generate pgbouncer/userlist.txt (see userlist.txt.example).
#   3. Put this stack on the SAME docker network as timescale_db so `timescale_db`
#      resolves (the tracksolid stack's network — the one with the 10.0.15.x addrs).
#   4. `docker compose -f pgbouncer/docker-compose.yml up -d`
#   5. Repoint each app's DSN host:port from timescale_db:5432 → pgbouncer:6432
#      (same dbname/user/password) and redeploy it. Migrate the SUPERUSER app pools
#      first — they are the heaviest consumers.
services:
  pgbouncer:
    image: edoburu/pgbouncer:latest      # pin to a digest/tag in prod
    container_name: pgbouncer
    restart: unless-stopped
    networks: [dbnet]
    ports:
      - "6432:6432"                       # drop this if only in-network apps connect
    volumes:
      - ./pgbouncer.ini:/etc/pgbouncer/pgbouncer.ini:ro
      - ./userlist.txt:/etc/pgbouncer/userlist.txt:ro
    logging:
      driver: json-file
      options: { max-size: "10m", max-file: "5" }
    healthcheck:
      # `SHOW VERSION` on the admin console proves PgBouncer is accepting connections.
      test: ["CMD-SHELL", "psql -h 127.0.0.1 -p 6432 -U pgbouncer_auth pgbouncer -tAc 'SHOW VERSION' || exit 1"]
      interval: 30s
      timeout: 3s
      retries: 3
      start_period: 10s

networks:
  # Attach to the EXISTING network that can reach timescale_db (external = pre-created
  # by the tracksolid/Coolify stack). Set the real name here, e.g. the network shown by
  #   docker inspect timescale_db --format '{{range $k,$v := .NetworkSettings.Networks}}{{$k}}{{"\n"}}{{end}}'
  dbnet:
    external: true
    name: CHANGE_ME_tracksolid_db_network