Closes#94. The local compose's event-subscriber lacked Acl__BaseUrl (and the acl dependency) that the canonical compose sets (#78) — so it threw Missing configuration 'Acl:BaseUrl' and exited on startup, which also knocked over podman-compose's bring-up of the rest of the stack (the frontends were left uncreated). Adds the env + dependency, matching docker-compose.yml.
How verified
Recreated event-subscriber from the fixed compose locally — it now starts healthy, and the three portals come up (self-service :8140, openbaar :8141, behandel :8142). docker compose config valid.
Note (separate, not fixed here)
On rootless podman the portal→BFF nginx proxy still 502s (resolver 127.0.0.11 is Docker's embedded DNS; podman uses its own), and podman-compose orchestration of this dependency graph is flaky — both are pre-existing local-engine limitations, clean on Docker Desktop / CI. Tracking separately.
## What & why
Closes #94. The local compose's `event-subscriber` lacked `Acl__BaseUrl` (and the `acl` dependency) that the canonical compose sets (#78) — so it threw `Missing configuration 'Acl:BaseUrl'` and exited on startup, which also knocked over podman-compose's bring-up of the rest of the stack (the frontends were left uncreated). Adds the env + dependency, matching `docker-compose.yml`.
## How verified
Recreated `event-subscriber` from the fixed compose locally — it now starts healthy, and the three portals come up (self-service :8140, openbaar :8141, behandel :8142). `docker compose config` valid.
## Note (separate, not fixed here)
On **rootless podman** the portal→BFF nginx proxy still 502s (`resolver 127.0.0.11` is Docker's embedded DNS; podman uses its own), and podman-compose orchestration of this dependency graph is flaky — both are pre-existing local-engine limitations, clean on Docker Desktop / CI. Tracking separately.
The local compose's event-subscriber lacked Acl__BaseUrl (and the acl dependency), so it threw
'Missing configuration Acl:BaseUrl' at startup — a parity gap vs the canonical compose (#78).
Its non-zero exit also destabilised podman-compose's bring-up of the rest of the stack.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
What & why
Closes #94. The local compose's
event-subscriberlackedAcl__BaseUrl(and theacldependency) that the canonical compose sets (#78) — so it threwMissing configuration 'Acl:BaseUrl'and exited on startup, which also knocked over podman-compose's bring-up of the rest of the stack (the frontends were left uncreated). Adds the env + dependency, matchingdocker-compose.yml.How verified
Recreated
event-subscriberfrom the fixed compose locally — it now starts healthy, and the three portals come up (self-service :8140, openbaar :8141, behandel :8142).docker compose configvalid.Note (separate, not fixed here)
On rootless podman the portal→BFF nginx proxy still 502s (
resolver 127.0.0.11is Docker's embedded DNS; podman uses its own), and podman-compose orchestration of this dependency graph is flaky — both are pre-existing local-engine limitations, clean on Docker Desktop / CI. Tracking separately.