The new default Coolify labels appear less optimal for applications with multiple containers

[NBruhno]

Describe the feature you would like to see

Hello 👋

In v10, a nice little QoL change was added which uses the coolify.resourceName if present as a label on the container to name it in the UI. This works well for applications with just one running container e.g. Dockerfile applications. It is however less than optimal for applications with multiple containers, e.g. a docker compose application. Each container in an application with multiple containers have the label coolify.resourceName, which will be identical to the name of the whole application, so they all show up with the same name in the UI.

An example of how it currently looks in my UI.

Example of coolify labels that can be used for naming, on an application with multiple containers

"coolify.name": "web-dg8oo4gwkssc8ks80wogs44k",
"coolify.resourceName": "monitor-glitchtip",
"coolify.service.subName": "glitchtip-website",
"coolify.service.subType": "application",
"coolify.serviceName": "glitchtip-website",
"coolify.type": "service",

Describe how you would like to see this feature implemented

I propose that instead of always defaulting to the coolify.resourceName, it should use the coolify.service.subName instead when present, which is only present in these kind of application types (AFAIK) which are then named individually.

Describe any alternatives you've considered

I think coolify.serviceName would work as well, it appears to function as coolify.service.subName if present, otherwise it is coolify.resourceName.

[amir20]

@javierperezm added the original PR. I don't use Coolify. So PR appreciated @NBruhno

[NBruhno]

I can have a look at it maybe this weekend, assuming Go doesn't intimidate me too much 😅

[amir20]

This was the PR #4384

[javierperezm]

Hello @NBruhno 👋

I can take a look at it or help you with your PR. As you prefer.

[NBruhno]

Hey @javierperezm

If you have time you are more than welcome to just go ahead and implement it, I would appreciate that

[javierperezm]

@NBruhno How would you prefer it to be displayed? I see three possible solutions:

1. Simply display coolify.service.subName instead of coolify.resourceName
2. Display: coolify.resourceName > coolify.service.subName (Example: "monitor-glitchtip > glitchtip-website")
3. Use coolify.resourceName as the group name, and include all coolify.service.subName within it

I look forward to your comments.

[NBruhno]

@javierperezm I don't know if the way it is grouped should be changed, I don't have any strong preference for how that behaves since I don't have multiple projects in my setup.

Both option 1 and 2 would work well for me. I always name my own sub services prefixed with the application but I don't know if that's the right pattern or if other use it.

If you go with option 1, I would suggest using coolify.serviceName instead, since that appears to prioritise the sub name if present and otherwise uses the resource name.

If you go with option 2, keep in mind that coolify.service.subName is only present if the application has sub services.

Whichever of the solutions you choose I would be happy regardless.

[javierperezm]

@amir20 what do you think?

[amir20]

I don't use Coolify so you all would know better than me.

If you go with option 1, I would suggest using coolify.serviceName instead, since that appears to prioritise the sub name if present and otherwise uses the resource name.

This does make sense to me. But @javierperezm @NBruhno you all can ultimately decide what makes sense. It's always hard to have one solution that makes everybody happy. I would go with the most common usage and allow a way for people to configure as needed.

[fa-sharp]

Just to add my 2 cents - I have a bunch of different Docker Compose services running in Coolify, and I would prefer the containers to be grouped by service (as they were in the previous Dozzle version v9). That way, for example, if there are multiple redis containers named just 'redis' running on different services, it will be clear which one belongs to which Coolify service.

Otherwise, if the UI only shows the serviceName or subName of the containers, that may make it difficult to differentiate things for people running a lot of services in Coolify.