Umbrel currently overwrites each app’s docker-compose.yml on update and does not load a corresponding docker-compose.override.yml, even though this file is preserved in app-data. Adding conditional support, loading the override only if the file exists, would allow users to extend or customize app configurations (extra services, environment overrides, reverse proxy integration, etc.) without needing to fork apps or reapply patches after every update.
This small change would align Umbrel with standard Docker Compose behavior while keeping the default experience unchanged for users who do not use overrides. It would significantly improve extensibility and maintainability for advanced users, with minimal impact on the core system.
Umbrel currently overwrites each app’s docker-compose.yml on update and does not load a corresponding docker-compose.override.yml, even though this file is preserved in app-data. Adding conditional support, loading the override only if the file exists, would allow users to extend or customize app configurations (extra services, environment overrides, reverse proxy integration, etc.) without needing to fork apps or reapply patches after every update.
This small change would align Umbrel with standard Docker Compose behavior while keeping the default experience unchanged for users who do not use overrides. It would significantly improve extensibility and maintainability for advanced users, with minimal impact on the core system.