# One-shot seed job for the production stack, kept out of
# docker-compose.prod.yaml so that bringing production up, or restarting it,
# never reloads the catalogue. Run it deliberately, once the prod stack is
# healthy:
#
#   docker compose --env-file web/.env.prod -f web/docker-compose.prod.seed.yaml run --rm --build database.seed
#
# Its own project name keeps it from treating the prod stack's containers as
# orphans; it joins the prod network to reach sqlserver and seaweedfs.
name: biergarten-prod-seed

services:
  database.seed:
    env_file: ".env.prod"
    image: database.seed
    container_name: prod-env-database-seed
    build:
      context: ./backend
      dockerfile: Database/Database.Seed/Dockerfile
      args:
        BUILD_CONFIGURATION: Release
        APP_UID: 1000
    environment:
      DOTNET_RUNNING_IN_CONTAINER: "true"
      DB_SERVER: "${DB_SERVER}"
      DB_NAME: "${DB_NAME}"
      DB_USER: "${DB_USER}"
      DB_PASSWORD: "${DB_PASSWORD}"
      SEAWEEDFS_SERVICE_URL: "${SEAWEEDFS_SERVICE_URL}"
      SEAWEEDFS_ACCESS_KEY_ID: "${SEAWEEDFS_ACCESS_KEY_ID}"
      SEAWEEDFS_SECRET_ACCESS_KEY: "${SEAWEEDFS_SECRET_ACCESS_KEY}"
      SEAWEEDFS_BUCKET: "${SEAWEEDFS_BUCKET}"
    restart: "no"
    networks:
      - prodnet

networks:
  prodnet:
    name: biergarten-prodnet
    external: true