We use and love Docker Compose in development environments. However in production we need to use some more sophisticated orchestration tools. As a result we have two distinct configuration files that describe the same containers relations.
To follow the DRY principle we need a tool transform a compose yml file (used in dev environments) into a descriptor for the tools we use in production :
To achieve that we could add a new Docker Compose command (export
):
compose -f compose.yml export --format mesos-marathon
or build an application written in GO packaged as a docker image (composexp
):
docker run -it composexp --file compose.yml --format mesos-marathon
or a web application that exposes some REST API to transform a yml/json from one format to anothe with a web UI form that make use of them.