Niek Otten
b349dff496
Drops the inline-build images for the upstream services. The compose now references the published images directly (openzaak/open-zaak, openzaak/open-notificaties, keycloak, curl, flowable-rest) with no build for them, and the config they need is streamed into external named volumes by infra/seed-config.sh: rr-oz-config -> oz-init /app/setup_configuration (data.yaml) rr-kc-realms -> keycloak /opt/keycloak/data/import (realm exports) rr-fl-bpmn -> flowable-init /work (registratie.bpmn) How: the seeder creates each volume, `docker create`s a throwaway helper that mounts it, `docker cp`s the files in, and removes it. docker cp streams over the Docker API, so it works in Docker-in-Docker (the CI runner) where bind mounts mount empty. It uses plain `docker create`/`cp` — NOT `docker compose create`, which podman-compose (local dev) lacks. `external: true` fixed names keep the volumes identical across docker compose and podman-compose. Consequence: bare `docker compose up` no longer self-seeds, so use `make up` (seeds then starts). Every `*-up` target seeds first; `*-down` removes the external volume. acl/bff are still built (they're our apps, not upstream images). Verified end-to-end on podman-compose: `make keycloak-up` seeds rr-kc-realms, the upstream Keycloak mounts it, and --import-realm imports all four realms (digid realm returns 200). Seeder runs in ~2s. Docs updated: gitea-actions-gotchas.md, ci.md, openzaak.md. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
71 lines
2.3 KiB
YAML
71 lines
2.3 KiB
YAML
# Flowable (S-03): the flowable-rest engine on Postgres.
|
|
# The registratie.bpmn model is deployed via the REST API on startup by flowable-init.
|
|
#
|
|
# docker compose -f infra/flowable/docker-compose.yml up -d
|
|
# # REST API (basic auth) under http://localhost:8090/flowable-rest/service/
|
|
#
|
|
# Host port 8090 (8000/8001/8080/8180 are taken by OpenZaak/NRC/BFF/Keycloak).
|
|
services:
|
|
flowable-db:
|
|
image: docker.io/library/postgres:16
|
|
environment:
|
|
POSTGRES_USER: flowable
|
|
POSTGRES_PASSWORD: flowable
|
|
POSTGRES_DB: flowable
|
|
volumes:
|
|
- flowable-db:/var/lib/postgresql/data
|
|
healthcheck:
|
|
test: ["CMD-SHELL", "pg_isready -U flowable -d flowable"]
|
|
interval: 5s
|
|
timeout: 3s
|
|
retries: 10
|
|
networks: [cg]
|
|
|
|
flowable-rest:
|
|
image: docker.io/flowable/flowable-rest:latest
|
|
environment:
|
|
SPRING_DATASOURCE_DRIVER-CLASS-NAME: org.postgresql.Driver
|
|
SPRING_DATASOURCE_URL: jdbc:postgresql://flowable-db:5432/flowable
|
|
SPRING_DATASOURCE_USERNAME: flowable
|
|
SPRING_DATASOURCE_PASSWORD: flowable
|
|
ports:
|
|
- "8090:8080"
|
|
depends_on:
|
|
flowable-db:
|
|
condition: service_healthy
|
|
networks: [cg]
|
|
|
|
# Deploys workflows/registratie.bpmn via the REST API once flowable-rest is up.
|
|
# Idempotent: skips if a deployment named "registratie" already exists.
|
|
flowable-init:
|
|
image: docker.io/curlimages/curl:latest
|
|
restart: "no"
|
|
# registratie.bpmn is streamed into this external volume by infra/seed-config.sh.
|
|
volumes:
|
|
- fl-bpmn:/work:ro
|
|
command:
|
|
- sh
|
|
- -c
|
|
- |
|
|
base=http://flowable-rest:8080/flowable-rest/service/repository/deployments
|
|
until curl -sf -u rest-admin:test "$$base" >/dev/null 2>&1; do echo "waiting for flowable-rest..."; sleep 3; done
|
|
if curl -s -u rest-admin:test "$$base?name=registratie" | grep -q '"name":"registratie"'; then
|
|
echo "registratie already deployed; skip"
|
|
else
|
|
curl -sf -u rest-admin:test -F 'file=@/work/registratie.bpmn;filename=registratie.bpmn' "$$base" >/dev/null && echo "deployed registratie"
|
|
fi
|
|
depends_on:
|
|
flowable-rest:
|
|
condition: service_started
|
|
networks: [cg]
|
|
|
|
volumes:
|
|
flowable-db:
|
|
# populated out-of-band by infra/seed-config.sh (docker cp) — see that script.
|
|
fl-bpmn:
|
|
external: true
|
|
name: rr-fl-bpmn
|
|
|
|
networks:
|
|
cg:
|