Looking at this structure - there's a "main" docker-compose file which includes small, "by-service" compose files (in compose folder).
However, despite I see the use of Extension Fields (i.e. <<: *common-keys-core in archive folder files) - I don't see it's being used as part of this divide strategy.
Is this possible?
E.g.
docker-compose-ws.yml:
...
# Keys common to some of the core services that we always to automatically restart on failure
x-common-keys-core: &common-keys-core
networks:
- npm_proxy
security_opt:
- no-new-privileges:true
restart: always
...
include:
...
- compose/$HOSTNAME/portainer.yml
...
Hey,
Looking at this structure - there's a "main" docker-compose file which includes small, "by-service" compose files (in
compose
folder).However, despite I see the use of Extension Fields (i.e.
<<: *common-keys-core
inarchive
folder files) - I don't see it's being used as part of this divide strategy. Is this possible?E.g.
docker-compose-ws.yml
:portainer.yml
: