Currently we try to mimic the stack of https://github.com/it-at-m/refarch-templates by providing a "copy" of the docker-compose file as a docker-compose-refarch-base.yml
However this assumes we will try to keep both stacks in sync in the future (which has to be done manually).
Since the development for the gateway and the integrations itself don't need the same setup as when working with the templates, we should decouple those stacks and handle them separately.
Desired solution
Merge docker-compose-refarch-base.yml and docker-compose.yml and only keep relevant images for development.
Considered alternatives (optional)
No response
Additional context (optional)
No response
No duplicate
[X] I confirm that this issue is not a duplicate
Code of Conduct
[X] I agree to follow this project's Code of Conduct
Relevant component
No response
Problem description (optional)
Currently we try to mimic the stack of https://github.com/it-at-m/refarch-templates by providing a "copy" of the docker-compose file as a
docker-compose-refarch-base.ymlHowever this assumes we will try to keep both stacks in sync in the future (which has to be done manually). Since the development for the gateway and the integrations itself don't need the same setup as when working with the templates, we should decouple those stacks and handle them separately.Desired solution
Merge
docker-compose-refarch-base.ymlanddocker-compose.ymland only keep relevant images for development.Considered alternatives (optional)
No response
Additional context (optional)
No response
No duplicate
Code of Conduct