Nicolas 47e84e131b Remove hardcoded credentials from committed env/compose files ... .env.example and apps/api/.env.example had a real usable default credential pair (batchcooking/batchcooking) baked in, and docker-compose.yml fell back to the same values via ${VAR:-default} if .env was missing. Neither should ship a working credential: - .env.example / apps/api/.env.example now use "changeme" placeholders that must be edited before use. - docker-compose.yml uses ${VAR:?...} instead of ${VAR:-default} for POSTGRES_USER/PASSWORD/DB, so compose fails loudly if .env isn't set up rather than silently falling back to a guessable credential. Healthcheck reads the container's own env var ($$POSTGRES_USER) instead of duplicating the value in the compose file. - README updated to say .env.example must be edited, not just copied. Verified: `docker compose config` fails with a clear message when .env is absent, and resolves correctly once .env is filled in.		2026-08-16 10:40:07 +02:00
..
api	Remove hardcoded credentials from committed env/compose files	2026-08-16 10:40:07 +02:00
web	Scaffold generic pnpm monorepo (api + web + shared)	2026-08-16 10:18:48 +02:00