The title might not be accurate but here is my issue:
- I'm highly dependent on compose
labels. There are multiple services running on my servers which gets auto configured based on the labels on containers.
One benefit which Komodo could bring, that I don't need to manually manage multiple - almost identical - compose files.
Example:
The whole compose file deployed to two different hosts only differs in label keys & values.
Server 1:
labels:
service.server_1.name: server1
...
Server 2:
labels:
service.server_2.name: server2
...
Value can be easily solved by moving it to an env and specifying it in the stack .env file.
However for keys, you can't add variables as docker compose does not support them: docker/compose#3108 (comment)
The same stands for volume mappings. Most of the time the volumes on similar containers are the same, but in off-case scenarios I might need to add additional volumes to one container. Right now this can be only be done with separate compose files.
It would be great if some kind of internal Komodo templating would be available (like Jinja2 templates) which will be interpolated before passing on to the host & periphery. That way, a base compose could be overwritten with custom keys & volumes, etc...
The title might not be accurate but here is my issue:
labels. There are multiple services running on my servers which gets auto configured based on the labels on containers.One benefit which Komodo could bring, that I don't need to manually manage multiple - almost identical - compose files.
Example:
The whole compose file deployed to two different hosts only differs in label keys & values.
Server 1:
labels:
service.server_1.name: server1
...
Server 2:
labels:
service.server_2.name: server2
...
Value can be easily solved by moving it to an env and specifying it in the stack .env file.
However for keys, you can't add variables as docker compose does not support them: docker/compose#3108 (comment)
The same stands for volume mappings. Most of the time the volumes on similar containers are the same, but in off-case scenarios I might need to add additional volumes to one container. Right now this can be only be done with separate compose files.
It would be great if some kind of internal Komodo templating would be available (like Jinja2 templates) which will be interpolated before passing on to the host & periphery. That way, a base compose could be overwritten with custom keys & volumes, etc...