docker-compose.yml

# Local development database.
#
#   docker compose up -d                        start an empty Postgres
#   docker compose --profile app up --build -d  start Postgres and the app on 8080
#   docker compose down                         stop it (data is kept)
#   docker compose down -v                      stop it and delete all data
#
# Works the same on Windows, macOS and Linux, so nobody needs a local
# Postgres install. Credentials below are development-only defaults and are
# deliberately overridable - do not put real credentials in this file or in
# application.properties, override them with a .env file instead.
#
# The container starts empty on purpose. It used to mount
# db/V1__initial_schema.sql as an initdb script, which meant the schema had
# two owners: the entrypoint applied V1 and Flyway then had to be told to
# tolerate a database it had never migrated. Flyway owns it now, so the app
# creates the schema on its first start and there is one place a table can
# come from. Volumes created before this change are unaffected.

services:
  db:
    image: postgres:16
    container_name: faf-db
    # Come back automatically after a Docker or machine restart, so the database
    # is not left down while something that depends on it is brought back up.
    restart: unless-stopped
    environment:
      POSTGRES_USER: ${POSTGRES_USER:-clanadmin}
      POSTGRES_PASSWORD: ${POSTGRES_PASSWORD:-devpassword}
      POSTGRES_DB: ${POSTGRES_DB:-clan_management}
    # Published on 127.0.0.1 only, so the database is reachable from this machine
    # and not from everyone else on the same network (a laptop on campus wifi).
    # The app container still reaches it as db:5432 over the compose network.
    ports:
      - "127.0.0.1:${POSTGRES_PORT:-5432}:5432"
    volumes:
      - faf-db-data:/var/lib/postgresql/data
    healthcheck:
      test: ["CMD-SHELL", "pg_isready -U ${POSTGRES_USER:-clanadmin} -d ${POSTGRES_DB:-clan_management}"]
      interval: 5s
      timeout: 5s
      retries: 12


  app:
    build: .
    container_name: faf-app
    profiles: ["app"]
    depends_on:
      db:
        condition: service_healthy
    environment:
      SPRING_DATASOURCE_URL: jdbc:postgresql://db:5432/${POSTGRES_DB:-clan_management}
      SPRING_DATASOURCE_USERNAME: ${POSTGRES_USER:-clanadmin}
      SPRING_DATASOURCE_PASSWORD: ${POSTGRES_PASSWORD:-devpassword}
      # dev switches on the in-memory accounts, and admin/admin is a site
      # administrator there, so this default is for demos only
      SPRING_PROFILES_ACTIVE: ${SPRING_PROFILES_ACTIVE:-dev}
      # inside the container the app has to listen on the container's own
      # interface, the dev profile's 127.0.0.1 would leave it unreachable
      SERVER_ADDRESS: 0.0.0.0
    # 127.0.0.1 only: with the dev profile on, anyone who could reach this port
    # could sign in as admin/admin and use the admin console
    ports:
      - "127.0.0.1:8080:8080"

volumes:
  faf-db-data: