[Feature Request] A widget to show the most recent release of a repository

[Aandree5]

Description

Would a widget that lists certain docker container repositories with when they were last updated and the most recent version be something people would be after?

I would like to open my dashboard and see when an update was last released for the repositories I want to follow (this could work with docker hub, github, etc..). I like to update my containers manually and this would give me a good insight into available releases.

I know Watchtower and WUD do something like this, but I have several docker hosts and don't find it efficient to run seveal instaces of either software to just let me know of realeases (I know WUD accepts many hosts but I need the docker socket available over tcp and is another thing I don't find it's worth it just for this use case).

I can even to the work, just don't want to do it and having to maintain a separate repository just for that. Just want to see if this is something more people would want.

Other

No response

[markalex2209]

I find the idea interesting. But to be completely honest, I don't see how this can be integrated into homepage, while keeping original goal and design intact.

Also, there is this FR with similar idea.

[Aandree5]

This is what I noticed when I started looking into the code. I was thinking maybe a custom proxy handler but I'm not sure it would work.

[malys]

newrelease it's to my mind a solution.
With loop of http get queries it's possible

[Aandree5]

Thank you for the sugestion, I hadn't though about this. I would prefer a solution without needing a 3rd party tool (in the sense of it would probably need configuring the repositories in two places), but if it cannot be done via the current design I will look into this as an option.

[malys]

I was looking for a solution to manage release notifications and At the end, I use newrelease. why:

• many many repositories support (docker, npm, mvn ...)
• provides cli and api for automation
• send email

I define my list of release to watch in one place "newreleases" and i use cli or api to consume information.

I have tried to integrate it but I need to loop on different api methods.

[Aandree5]

I wasn't aware of the API feature in it. I will be looking into this as an option.

[Aandree5]

I went ahead and tried to look into implementing this. As already discussed above, the tool wasn't really designed to flow this way, it was supposed to call a single API per widget (unless I missed something).

By creating a custom proxy handler (without much change from the generic) I was able to implement a working solution, but because it deviates a bit from the original intended design I'm not sure it would be accepted (even if many people were after it).

The error is testing a different repository that I've not setup the enpoint yet
We could easilly type a version regex to limit the "types of version" we are looking for, no regex just gives the most recent

Before I clean the code and make it look/work properly I just wanted to see if this way of flowing would be accepted. The major issue here is potentialy having many different repositories to go to (i.e. different APIs), so my plan was to do something like this (for the API definition):

this will then allow the endpoints to work as different API calls, and the parameters would get replaced on the custom proxy, like so:

Here I'm leveraging the query values (which are not really used because no params have been defined in the API definition). The best solution here would be to have a pathParam for example, I just didn't want to change the core code if not needed.

The call to useWidgetAPI currently looks like this:

[malys]

In my case, i will to try to create a custom api endpoint to expose newreleases information to unique call and after that use custom api widget

[Aandree5]

This is what I was thinking from the messages you posted above, I think it's a good idea, specially for people that already user newreleases.io
I was just thinking of a simpler widget more for people that don't currently use newreleases.io (or don't want to depend on it for some reason) where they could simply "follow" a few repositories (maybe the most important ones) releases.

[Aandree5]

I have an update to see if this would be interesting. Thought about doing some work to better explain and show what I'm envisioning.

This is the base idea, from the left (some points will be explained further down):

 - The repository provider logo
 - The owner/namespace for the repository
 - The repository name
 - The Regex used to match the version
 - The most recent release version
 - A mark/highlight of the repository as defined in the yaml file
 - How long ago as the release been published

Here's some other examples:
- Sorted by name

- Sorted by provider

- Two Columns

The yaml file is looking something like this:

• iconColour: allows to pick the colour for the provider logos (thinking of it now, should probably be called logosColours )
• twoColumns: allow to show the list in two columns, will limit information shown but be more compact
• githubToken: the token to use for rate limiting purpuses
• highlightRecent: if empty nothing will change, otherwise it can have a value of time (i.e. 10h, 5d, 2w, 1m, 1y) to highlight any repository younger that this value, a way to try and pay attention only to the most recent releases wihtout having to store any data
• sort: how to sort the list, current allowed values are provider, name and releaseDate
• repositories: list of repositories to query with the following pattern <provider>@<owner>/<repositoryName>:<versionRegex>
  • <provider>: the repository provider (if empty defaults to github)
  • <owner>/<repositoryName>: the actual repository, on github is the owner and the repository name, on docker is the namespace and the repository name
  • <versionRegex>: a regex to help flter the versions retrieved, so in the homepage repository example, it will only look for releases that start with the letter v have at least one digit and then more characters, this helps filter out releases like latest or dev (in docker hub). On github they are usually not needed I would say, although there are some exceptions, for owncloud ocis they actually release a Pre-Release which will be more recent so with something like this ^v\d+(?!.*rc).*$ that could be excluded. I've only added them here mostly for testing and exmaples.

There's other things I was thinking like:

• Showing only X repositories and to collapse any repository past that point.
• Only showing the highlighted repositories via the highlightRecent variable, basically clearing the view and only showing the releases in the last week for example, or this month.

Would like to know what people think and if they would find this useful or have any feedback. Still needs some work done and code to be cleaned a bit, but it's mostly there.

[malys]

FYI: with custom api and newreleases
I'm very desappointed, custom api is too limited to make something beautiful.
Generic solution without developping widget (supporting 30 providers)

[Aandree5]

That's a shame it's not more customisable.
On the flip side it's much quicker and already supports probably all providers!
A custom widgets is something that can always follow from that, part of it is done.

[Aandree5]

Think I got it sorted now, if people are interested in this I can submit a pull request.
I've reformated the yaml structure, and added repository logos, the refreshInterval property (so not to spam the providers, defaulted to 30 minutes) and the hability to show only the top X repos.

This is what it looks like:

And the yaml:

[malys]

PR will perfect

[Aandree5]

Sadly I don't think the PR would be accepted until it has 20 up votes