feat(infra): OpenZaak + Postgres + Redis up in compose (refs #10) #40
Reference in New Issue
Block a user
Delete Branch "feat/10-openzaak-compose"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
First stage of S-01 (#10): the OpenZaak stack comes up in compose.
infra/openzaak/docker-compose.yml— PostGIS + redis + migrate-init + OpenZaak API + celery worker (lean adaptation of upstream; images qualified for rootless Podman).Verified locally: migrations run;
GET /admin/→ 302,GET /zaken/api/v1/→ 200, unauthGET /zaken/api/v1/zaken→ 403 PermissionDenied (proper ZGW fout — auth enforced).⚠️ Finding: the issue says "401", but OpenZaak returns 403 for missing JWT. Intent (auth enforced) is met; #10 text should be corrected to 403.
Remaining for S-01 (so this
refs, not closes, #10): BIG catalogus + leanBIG-registratiezaaktype +bsneigenschap seed + JWT client to list zaaktypen; and Open Notificaties. Recommend splitting #10 into sub-slices.🤖 Generated with Claude Code