.env

# Compose defaults for a bare `docker compose ...` run from the REPO ROOT.
# (docker/.env is the identical file for runs from the docker/ directory —
# Compose reads `.env` from the project directory, which is the directory of
# the compose file it is given. Keep the two in sync.)
#
# Every service in docker/docker-compose.yml is profile-gated, so without this
# a bare `docker compose up` would fail with "no service selected". This makes
# the single-node SQLite deployment the DEFAULT:
#
#   docker compose up            ==  docker compose --profile single-node up
#
# A `--profile` on the command line REPLACES this value (it does not add to
# it), so `docker compose --profile postgres up` starts the postgres profile
# ONLY — `server-sqlite` stays down and cannot collide with `server-postgres`
# on ${CHANCELA_HOST_PORT:-8080}. An exported COMPOSE_PROFILES in your shell
# also wins over this file.
#
# This file is COMMITTED and holds no secrets. Deployment secrets live in the
# `chancela-secrets` volume (see docker/secrets-init.sh and
# docker/secrets/README.md), never here. Local-only overrides belong in
# .env.local or your shell environment, both of which stay gitignored.
COMPOSE_PROFILES=single-node

# Profiles are two axes and they compose: a BACKEND (`single-node` or
# `postgres`, each enabling exactly one app service) plus additive SIDECARS
# (`worker`). The worker mounts the app's data volume, and which volume that is
# depends on the backend — so the postgres+worker combination needs:
#
#   CHANCELA_APP_DATA_VOLUME=chancela-app-data \
#     docker compose --profile postgres --profile worker up -d
#
# Left unset it defaults to `chancela-data`, which is correct for `single-node`.
#CHANCELA_APP_DATA_VOLUME=chancela-data

# The `postgres` profile's projector role initializer revokes database-global
# PUBLIC ACLs (CONNECT/CREATE/TEMPORARY on the database, CREATE on schema
# public) and REFUSES to run until you acknowledge that the database is
# dedicated to Chancela. Uncommenting the line below is the cross-platform way
# to acknowledge it — Compose reads this file identically on Windows, macOS and
# Linux, unlike the `VAR=value docker compose ...` prefix, which is bash syntax
# and is NOT an environment assignment in PowerShell.
#
# It ships COMMENTED OUT on purpose: the gate must stay fail-closed until an
# operator opts in deliberately. The bundled `postgres` profile creates its own
# dedicated `chancela` database, so there this is the expected answer; never set
# it for a database shared with another application.
#CHANCELA_PROJECTOR_DEDICATED_DATABASE=true