Support for Docker Compose override files

[mathiaspl20]

Feature Request

CrowdSec Manager currently expects only a single docker-compose.yml file to be mounted at /app/docker-compose.yml. It uses this file internally for stack management, service visibility, backups, and other features.

There is no support or documentation for Docker Compose override files.

It would be very useful if support for standard Docker Compose override files was added, so the manager can see the fully merged configuration (base file + overrides).

This should include both the classic docker-compose.override.yml and the more modern compose.override.yml (without the docker- prefix), as used by current versions of Docker Compose.

Why it would be a relevant addition
Many users (including myself) prefer to keep the base docker-compose.yml clean and untouched - especially when it's taken from a repository or example.

I use an override file for:

Environment-specific settings (ports, resource limits, restart policies, logging, etc.)
Adding or overriding services
Changing container versions
Keeping sensitive or custom configuration separate
Making it easier to update the main stack without losing personal changes

Without override support, functionality seems to be limited, unless changes are merged into a main compose file, which is error-prone.

[hhftechnology]

@mathiaspl20 will think about, 90% of users dont separate compose file,
You are correct, i had similar approach in another project but i had to switch to api . but i am writing a multi proxy support in that i can take that approach. pitch in on your best approach, i can look into it.