Open andreaskoch opened 8 years ago
@andreaskoch what would the project name end up contributing to the final output? would it simply be prepending to the service name? can you provide an example?
If you were running both projects locally (using docker-compose, pre-transform), would it still conflict? (e.g. is this an actual problem with the transform project, or are the namespaces conflicting regardless and you just want a utility for automatically changing the names during transform?)
It would be great if you could add a project-name parameter to container-transform.
Currently the container names created by container-transform don't include the project name of the docker-compose file. This leads to collisions with other project using the same container name (e.g. "nginx").
I believe that usually one would not try to make the service names (or container names) globally unique like "projectxynginx" inside a docker-compose.yml.
Example
Run two similar projects on the same server: Both projects have a frontend named web and a backend named phpfpm:
Project A
Project B
If I now create systemd services for both projects using container-tranform I will get collisions because the docker containers of both projects have the same names:
Project A
Project B
... I always wanted to learn Python. Maybe this is the time for me so I can create a pull request for your project :smile: