T13.8: run the stack in Docker on a PC, local compose override and steps (D22); log BL-070

This commit is contained in:
2026-10-16 15:08:01 -07:00
parent bcef0e8145
commit ad1b8273c0
5 changed files with 111 additions and 0 deletions

View File

@@ -349,3 +349,24 @@ Alembic upgrade, downgrade, upgrade passed. Import check passed.
Result 2026-10-16: all Okta sync tests and `security_check.py` pass in the sandbox.
This task changes no frontend file.
## T13.8: run the stack in Docker on a PC
**Item:** D22 (`docs/waves/decisions-2026-10-16.md`), as a way to check T13.7 and later builds before a deploy.
**Done when:**
- [x] one command starts the api, the database and the web server from the shipped compose file plus `docker-compose.local.yml`
- [x] `http://localhost:8080/api/health` answers 200 and `/api/projects` answers 401 without a session
- [x] every migration runs on Postgres (head `8e2cb3003f8a`)
- [x] the api log shows the `Okta sync` startup line
- [x] the steps are in `DEPLOYMENT.md`, "Run the stack on your own PC"
- [x] the shipped `docker-compose.yml` and nginx config are not changed
Result 2026-10-16 (Docker Desktop 29.7.2, Compose 5.4.0, Windows): passed. Three
things in the shipped files stop a local run. The override handles the first two
and the third is logged:
1. The web server publishes no port (the host's reverse proxy reaches it). The override publishes 8080 on loopback.
2. An existing `proxy` network on a PC can have no gateway, and Docker then does not publish ports. The override uses its own bridge. The stock nginx `default.conf` also answers "localhost" first and the app server answers only wp.controls.dev, so the override removes the stock file and makes the app server the default.
3. The backup container cannot start on Windows: `scripts/entrypoint.sh` has CRLF line endings (BL-070). The override turns the backup service off.