Add version tag based update notification / integration of renovate or dependabot

[ln-12]

⚠️ Please verify that this feature request has NOT been suggested before.

• I checked and didn't find similar feature request

🏷️ Feature Request Type

UI Feature

🔖 Feature description

Currently, I have to use the docker version tag latest in my compose.yaml files and update them manually via the Update button.

My suggestion is to add some mechanism which automatically gets the latest version tag and provides me some UI to apply or ignore that update.

✔️ Solution

This might be possible with the integration of a tool like renovate or dependabot. Currently, I have already added all of my compose.yaml files to a git repository and run renovate daily. It then creates a PR that I can merge. Another action is then triggered to update the docker container on my server.

It would be nice to have all container handling in one place (= dockge). It seems like renovate can be run locally so that dockge could ask for updates according to a user defined schedule and use the received information to show an update hint in the according container tab (and ideally also send a notification).

In the end I image the following workflow:

• I setup my compose.yaml file using a X.Y.Z version tag instead of latest
• dockge runs renovate once a day and receives information about updates
• dockge sends a notification via mail (or any other channel) that contains a link to the dockge tab of the container that has an update
• I click on the link and can choose to apply or ignore that version
• if applied, dockge replaces the version tag in the compose.yaml file and pulls the image
• if ignored, dockge will only send me a notification for the next upate
• ideally I would also see the version history to make rollbacks easier

❓ Alternatives

I could for example use something like watchtower to automatically notify me of updates and/or pull the latest images.

Some downsides of this approach are:

• things might break as I cannot configure a major/minor update rule (not all containers use the format MAJOR.MINOR.PATCH)
• I do not see any changelog (and hint for breaking changes)
• it is hard to roll back as I don't see which version was used before

📝 Additional Context

No response