Allow custom Traefik middleware labels to override or merge with default labels

[Paillat-dev]

See also:

• https://discord.com/channels/459365938081431553/1279335972592685126/1279335972592685126

Problem Summary

• Custom Traefik middleware labels are overridden by default labels in Coolify for certain deployment types (predefined templates and docker-compose files).
• This prevents users from adding important middleware like Crowdsec or custom rate limiting to their services when using compose-based deployments.
• The issue doesn't occur when deploying from a Dockerfile.

Root Cause

Coolify generates its labels after user-defined ones for compose-based deployments, resulting in custom labels being ignored.

Impact

• Limited ability to implement additional security or performance measures using Traefik middlewares.
• Inconsistent behavior across different deployment methods.
• Reduced flexibility for users who prefer or require compose-based deployments.

Proposed Solutions (in order of preference)

1. Add a property for additional middlewares

   • Pros: Clean integration with Coolify's internal processes
   • Cons: Requires UI/UX changes and backend implementation

2. Implement a merging mechanism for middleware labels

   • Pros: Preserves both user-defined and Coolify-generated middlewares
   • Cons: Potential complexity in merging logic

3. Allow custom labels to override default ones

   • Pros: Simpler implementation
   • Cons: Potential breaking change for existing setups

Analysis

The proposed solutions address the core issue while maintaining different levels of backwards compatibility and user control. Solution 1 provides the cleanest integration but requires more development effort. Solution 2 offers a balanced approach but may introduce complexity. Solution 3 is the simplest but could disrupt existing deployments.

[Paillat-dev]

Solution 2 was fully implemented in #3637 Not the case actually

[qverkk]

@Paillat-dev i've had a similiar issue, i wanted to change the certresolver, update the traefik rules and add another router so i could secure an endpoint for only whitelisted IPs. For now i've set the Readonly labels to true, this is just a workaround and i'd be happy to have a feature as you've explained above