docs: explain how to check OpenZaak is running
CI / changes (push) Successful in 9s
CI / storybook-a11y (push) Successful in 16s
CI / lint (push) Successful in 11s
CI / frontend (push) Successful in 14s
CI / backend (push) Successful in 2m7s
CI / e2e (push) Successful in 2m42s
CI / semgrep (push) Successful in 1m4s
CI / api-client-drift (push) Successful in 1m44s
CI / changes (push) Successful in 9s
CI / storybook-a11y (push) Successful in 16s
CI / lint (push) Successful in 11s
CI / frontend (push) Successful in 14s
CI / backend (push) Successful in 2m7s
CI / e2e (push) Successful in 2m42s
CI / semgrep (push) Successful in 1m4s
CI / api-client-drift (push) Successful in 1m44s
docker compose up at the repo root does not start OpenZaak. A new reader could easily assume it does. Add a short section to backend/openzaak/README.md that shows how to check the four containers and how to curl OpenZaak directly, using the same probe bootstrap-catalogus.sh already relies on. Add one line to the root README pointing there. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
@@ -32,6 +32,9 @@ docker compose up
|
||||
# API + Swagger → http://localhost:5000/swagger
|
||||
```
|
||||
|
||||
This does not start OpenZaak. The BFF uses a local, in-memory case store instead. To run
|
||||
against a real OpenZaak, see [backend/openzaak/README.md](backend/openzaak/README.md).
|
||||
|
||||
Or run the pieces yourself:
|
||||
|
||||
```bash
|
||||
|
||||
Reference in New Issue
Block a user