[Feature Request] Service Group Layouts On Name

[Con1924]

Description

The settings.yaml > Layout feature is good but not for auto discovered services from docker lables as it requires manually adding to the layout. Would like the ability to order by name or have groups defined in services.yaml followed by auto discovered service groups.

Even better would be to have Groups and Sub Groups. Such as frontend and Backend, then have auto discovered groups inside a subgroup.

Other

We have backend services in a group, like traefik, homepage, watchtower and then groups for docker stack deloyments that are auto detected. To keep them organised we have to add to the settings.yaml> layouts section, making deployment more manual.

[glime-ai[bot]]

To address your request for improved organization of auto-discovered services in Homepage, including ordering by name and the ability to have groups and subgroups, I would like to provide some guidance based on the current functionality described in the documentation.

As of the latest information available, Homepage allows for the configuration of service groups and bookmark groups within the settings.yaml file, and these groups will sort based on the order in the layout block. However, the auto-discovery feature for Docker services relies on labels, and these services are automatically added to the Homepage without the need for manual entry in the settings.yaml file.

While the documentation does not explicitly mention the ability to order auto-discovered services by name or to create subgroups within auto-discovered groups, you can influence the order of services by using the weight field for discovered services. This allows you to assign a weight to each service, which can be used to sort them. The default weight for discovered services is 0, and for configured services, it is their index within their group scaled by 100.

To achieve a more organized layout with auto-discovered services, you could consider the following approaches:

1. Use the weight field: Assign weights to your auto-discovered services to control their order. This requires you to add labels to your Docker configurations.

2. Manual Grouping: If you want to maintain a specific order or create subgroups, you may need to manually add these groups to the settings.yaml file under the layout section. This approach goes against the auto-discovery principle but gives you full control over the organization.

3. Feature Request: If the current functionality does not meet your needs, you could submit a feature request to the Homepage repository on GitHub, suggesting the implementation of ordering by name for auto-discovered services and the ability to create subgroups within auto-discovered groups.

4. Custom Development: If you have development resources available, you could consider contributing to the Homepage project by developing this feature and submitting a pull request.

For now, you may need to rely on the existing features and consider manual adjustments or custom development to achieve the desired organization of auto-discovered services. Keep an eye on the project's repository for updates or responses to feature requests that may address your needs in the future.

---

Thanks for posting a discussion about homepage here on GitHub. Homepage now uses a fancy new AI tool thanks to our friends at Glime, so the answer below is the AI bot's attempt to answer your question. If you feel it's sufficient you can mark the answer and close this post, otherwise feel free to leave it open of course!

Thanks for using Homepage! ❤️

This comment was generated by Glime.

[github-actions[bot]]

This discussion has been automatically closed due to lack of community support. See our contributing guidelines for more details.

[github-actions[bot]]

This discussion has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns. See our contributing guidelines for more details.