feat: support compose.override.yaml files in docker-compose script

[BR-RedEnzian]

why this feature is useful

if you need to change e.g. ports of one or more services, using a compose.override.yaml file is update save.
in my case, i run my own mariadb server on my machine, so port 3306 is assigned to this server and i cant access the containered version of mariadb with DataGrip.

current behaviour

docker-compose does currently ignore compose.override.yaml files

after the changes

this change will add an override file (if it exists) to the docker compose command.

[what-the-diff]

PR Summary

• Inclusion of compose.override.yaml File
  The code was updated to automatically use the compose.override.yaml file, should one exist. This allows for increased flexibility and customization, improving ease of use for users who may need to modify certain configurations.

[markshust]

Hi @BR-RedEnzian,

Looks like a nice update, however that is kinda what the compose.dev.yaml file is for. That file overrides the base compose.yaml file, so you should be able to put anything in that file meant to override the base. Did you try that out?

Cheers,
Mark

[BR-RedEnzian]

Hi @BR-RedEnzian,

Looks like a nice update, however that is kinda what the compose.dev.yaml file is for. That file overrides the base compose.yaml file, so you should be able to put anything in that file meant to override the base. Did you try that out?

Cheers, Mark

Hi,

yes i know the .dev file but my problem is/was, that this file is overwritten whenever used the bin/update script.

with the override file, developers have a way to keep their changes for docker compose files even when updating.