Persist docker auto-discovered services

[r3mi]

Description

Hello,
thanks for this great dashboard !
I am trying automatic service discovery through Docker, it works great. However, when the container is down, the service disappears from the dashboard. Is there a way to "persist" it, so that the service remains in the dashboard, with the checks shown as failing ? (as if the service was declared through the config/services.yaml file)

homepage version

v0.8.8

Installation method

Docker

Configuration

No response

Container Logs

No response

Browser Logs

No response

Troubleshooting

installation is working fine

[glime-ai[bot]]

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 in the context, Homepage's automatic service discovery feature is designed to detect and display services that are currently running. When a service is down, it will not be displayed on the dashboard because the discovery relies on the presence of the service to show its status.

To achieve the behavior you're looking for, where a service persists on the dashboard even when it's down, you would need to manually declare the service in the config/services.yaml file. This way, the service will remain visible on the dashboard, and any checks or status indicators will show that the service is failing or offline.

Unfortunately, as of the knowledge cutoff date, there is no built-in feature in Homepage to persist automatically discovered services in the dashboard when they are down. You would need to use the manual configuration method to have persistent service entries.

If you need further assistance on how to manually configure services in the config/services.yaml file, please let me know, and I can provide more detailed instructions.

This comment was generated by Glime.

[github-actions[bot]]

This discussion has been automatically closed due to inactivity. 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.