The root docker-compose.yml (Postgres + backend service, used for local dev) should be checked against services/backend/.env.example's current defaults (DB name/user/password, CONTRACT_IDS seeding) to make sure they still match after recent backend changes (the $PORT/BIND_ADDR fix, etc.).
To do: run docker compose up -d postgres && cd services/backend && cargo run, confirm /health returns {"status":"ok",...} with zero manual env tweaking beyond copying .env.example to .env.
The root
docker-compose.yml(Postgres + backend service, used for local dev) should be checked againstservices/backend/.env.example's current defaults (DB name/user/password,CONTRACT_IDSseeding) to make sure they still match after recent backend changes (the$PORT/BIND_ADDRfix, etc.).To do: run
docker compose up -d postgres && cd services/backend && cargo run, confirm/healthreturns{"status":"ok",...}with zero manual env tweaking beyond copying.env.exampleto.env.