E2E Docker-Compose

[simonhir]

The current dev-stack with docker-compose currently contains only some services like tasklist and gateway. For better development experience it would be good to include at least every core service (tasklist, tasklist-backend, gateway, engine, connector) and probably also the lokal running integrations like s3 and mail. Adding new services also includes settings up a good profile structure for starting scenarios. Also as the docker-compose-file is growing it would be a good idea to split it up and use the include-functionality.

To be discussed

• Include Integrations?
• How to split docker-compose.yaml? (per service or per layer (db, services, ...))
• Also add tools like pgAdmin?
• Health-Checks?
  • Could fix kafka dying when zookeeper not ready

    Acceptance criteria

• All core services (and integrations?) are added to docker compose
• Good profiles are specified for the services
• The docker-compose file is good to read because of splitting or refactoring

[darenegade]

@simonhir Is this story ready 4 refinement?

[simonhir]

yes, i added the label