[Bug] Setting weight to 0 for a configured service doesnt result in it being sorted
Dart2112 opened this issue · comments
Description
https://gethomepage.dev/main/configs/docker/#ordering
That link explains that discovered services have a weight of 0 and that if two items have the same weight then they will be sorted alphabetically.
So I have added a service via the config and given it a weight of 0 expecting it to be sorted amongst the discovered services. But it ends up at the bottom. Settings its weight to -1 puts it at the top so I know that it is at least sorting by weight.
See attached screenshot
Cockpit is configured since it isn't a docker container, all other services are added via docker labels.
Steps to reproduce
- Have a group with discovered services added via docker-compose labels
- Add a configured service via services.yml
- Add a weight of 0 to the configured service
homepage version
v0.8.4 (32f28d3, Dec 27, 2023)
Installation method
Docker
Configuration
- System:
- Cockpit:
weight: 0
href: {REDACTED}
ping: {REDACTED}
description: Server Management Web UI
icon: /icons/cockpit.png
Container Logs
No response
Browser Logs
No response
Troubleshooting
I've tried adjusting the weight, setting it to -1 puts Cockpit at the top of the list, as does any negative integer.
All positive integers and 0 put it at the bottom of the list
Other
No response
Before submitting, I have made sure to
- Check the documentation
- Follow the troubleshooting guide (please include output above if applicable).
- Search existing issues and discussions.
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns.