Component
Hub
Describe the feature you would like to see
An option to either set a custom name/alias for a container or set which key should be used by the Hub to identify the container. These would replace the container name used in the graphs and table.
Motivation / Use Case
As containers accumulate it gets harder to identify them, and we don't always get to name them as we please. this leads to situation where a graph can have tens of containers and having no idea which is which.
As an illustration I attached a stolen screenshot from a recent PR by @titouv , his case is even worse than mine but basically we seem to be in the same situation : a Coolify with limited renaming options and a messy list.
Describe how you would like to see this feature implemented
I see 2 options to implement this :
1. Give an option to give an alias to containers:
In the name column of the "All Containers" section we could imagine an icon allowing to give an alias to the container. That alias would then be used by said section and graphs in the rest of the hub.
One issue might be that containers don't always redeploy using exactly the same name I think.
2. Give the choice to the user of what key should be used to set the container's identifier:
Since Beszel has access to the container's details (as seen in the details tab when we click on a container) we could imagine a setting on the settings page where the user could set which key he would want the containers to be identified by. In my case I think I would use the key "Labels" => "coolify.serviceName".
If the key doesn't exist the name would fallback to the container's name.
- might be more straightforward for the users but more challenging technically so I think 2. might be better
Screenshots
Category
UI / UX
Affected Metrics
Containers
Component
Hub
Describe the feature you would like to see
An option to either set a custom name/alias for a container or set which key should be used by the Hub to identify the container. These would replace the container name used in the graphs and table.
Motivation / Use Case
As containers accumulate it gets harder to identify them, and we don't always get to name them as we please. this leads to situation where a graph can have tens of containers and having no idea which is which.
As an illustration I attached a stolen screenshot from a recent PR by @titouv , his case is even worse than mine but basically we seem to be in the same situation : a Coolify with limited renaming options and a messy list.
Describe how you would like to see this feature implemented
I see 2 options to implement this :
1. Give an option to give an alias to containers:
In the name column of the "All Containers" section we could imagine an icon allowing to give an alias to the container. That alias would then be used by said section and graphs in the rest of the hub.
One issue might be that containers don't always redeploy using exactly the same name I think.
2. Give the choice to the user of what key should be used to set the container's identifier:
Since Beszel has access to the container's details (as seen in the details tab when we click on a container) we could imagine a setting on the settings page where the user could set which key he would want the containers to be identified by. In my case I think I would use the key "Labels" => "coolify.serviceName".
If the key doesn't exist the name would fallback to the container's name.
Screenshots
Category
UI / UX
Affected Metrics
Containers