this comes with a dedicated database and a rabbitmq service.
This is usable as long as we use the docker-compose.override.yml for now.
Should i go do the cascading?
isn't there a flag to the runner so that it does it itself?
Checked and no!
They are independent, but if we run stuff.
Is that why you drew the deps here?
we could be this env file is not part of the docker image building process, it's really part of the compose orchestration one. So it's not about 'put all config files in one location' actually.
At some point we may need/want to split the docker image generation away from the compose (orchestration) part.
yes they are. The dependency is there just so the swh/scheduler-worker image is built when starting the runner. Which is a reason why I said in my previous comment:
it's really is just a simple technical deps due to the fact both services share the same image and the fact we do use docker-compose to build them.
if we want to keep the exec command, we need it. And I'm inclined to think it's best to keep the exec statement instead of running the for loop from within the case block.