-
DescriptionHello folks New user of homepage trying to figure out what the heck is going wrong with my implementation. Any time I try to add anything into services.yaml the result is a unclickable box that only shows the name field. It also doesn't support using the server and container fields either for docker. I can use labels just fine on docker compose files but nothing in services.yaml. can someone please let me know what I might be missing? I have set log_level to debug and the logs say nothing I have also tried multiple docker hosts and there containers and have the same results even though labels work on those as well My Services.yaml
in the "test" group is the one cited in services.yaml my docker label one is under IaaS including a working widget. The Adguard 02 result happens if I try to do the docker service inclusion in services.yaml instead of docker labels as well just fyi new services.yaml for testing with another container without a widget
Same thing happens with it as well homepage versionv0.8.10 (0af975b) Installation methodDocker Configuration---
- Test:
- Adminer:
icon: adminer
href: "http://192.192.2.2"
description: Adminer test for example
server: dockerxx
container: adminer Container LogsNothing shows even with debug other than: Browser Logsno errors Troubleshootingsee description, these tests all pass it works using docker lables just fine but not services.yaml |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 1 reply
-
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! ❤️ Based on the information provided and the In your ---
- Test:
Adguard 02:
icon: adguard-home
href: "http://192.192.2.2"
description: Adguard Blackhole DNS 02(potato)
widget:
type: adguard
url: http://192.192.2.2
username: admin
password: PASSSSSSSSS And for the second ---
- Test:
Adminer:
icon: adminer
href: "http://192.192.2.2"
description: Adminer test for example
server: dockerxx
container: adminer Please note that each service under the After making these changes, try reloading your homepage instance and check if the services are displayed correctly. If you continue to experience issues, please refer to the documentation for the correct structure and examples of If you need further assistance, please provide additional details or error messages that you encounter after making the suggested changes. This comment was generated by Glime. |
Beta Was this translation helpful? Give feedback.
-
This discussion has been automatically closed because it was marked as answered. See our contributing guidelines for more details. |
Beta Was this translation helpful? Give feedback.
-
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. |
Beta Was this translation helpful? Give feedback.
So the AI is wrong and right at the same time. These yml files are not correct either but they were better than mine. They are missing the - in front of the service name(they use 4 spaces instead and that does NOT work i triple checked) and only 2 spaces of indent. I'm not quite sure why, and it doesn't make sense to me as far as my knowledge of yaml goes but, the services.yaml file works if you give 4 spaces below the name of the services for its information (see below) for an actual working file for my implementation