I did a test deploy in a VM on my laptop.
The current setup is a development installation from a docker-compose.yml file that has some dependencies.
It loads environment variables from a .env file. Which is no problem, because we do the same for ESAP and OIDC. It can be placed in the same 'shared' directory.
What is an issue with the current setup is that it occupies a number of ports (see portainer screenshot). And that it (ofcourse) doesn't connect to the Traefik router yet.
My advice would be to adapt the docker-compose file in the way that is done for ESAP-API, but also to keep the ESAP stacks separated with different docker-compose files. So that work/deployments of ESAP-API and ESAP-DB don't impact each other.
I committed all the work needed to get this working to the Traefik branch, and I now fixed the tests.
To make this work, I had to add a traefik network to the docker-compose file, this means that whenever one does not use Traefik, the network will still be created. This may or may nit be acceptable in terms of overhead.