Currently Im working on a new project using both docker and microservices for the first time... compose is a neat and convenient tool but the one thing I wish it had were the ability to decouple extended services/repos more cleanly, aka not have to put the links in the top level docker-compose.yml.
This would allow having a single "master" compse.yml that simple imports the necessary services and then builds them via their own docker-compose.yml...
When working with microservices this would allow spinning up an entire multi-service/app project in one command AND also allow still spinning up any individual service on it's own when working on that specific service... As it is right now you are forced to put links in the top-level repo/compose.yml and use extends, which makes it not possible to run compose locally unless you make a separate file...
Currently Im working on a new project using both docker and microservices for the first time... compose is a neat and convenient tool but the one thing I wish it had were the ability to decouple extended services/repos more cleanly, aka not have to put the links in the top level docker-compose.yml.
This would allow having a single "master" compse.yml that simple imports the necessary services and then builds them via their own docker-compose.yml...
When working with microservices this would allow spinning up an entire multi-service/app project in one command AND also allow still spinning up any individual service on it's own when working on that specific service... As it is right now you are forced to put links in the top-level repo/compose.yml and use extends, which makes it not possible to run compose locally unless you make a separate file...
Something like this would be sweet:
orchestrate.yml
OR
orchestrate.yml
service-content/docker-compose.yml
Which would make containers prefixed by the top-level import name e.g.
service-content_web-db_1
What are your thoughts on something like this?