TL;DR: is there an app that can alert me when a new version of some other app is available?

I have about 12 - 15 services (freshrss, heimdall, photoprism, Wordpress, etc) running using docker compose spread across 4 hosts. Through my self-hosting journey I’ve been burned a few times using “latest” images so I now pin app image versions within compose.

The problem then becomes that every couple of weeks, I have to go out to different GitHub’s, docker hub, etc. to see if a new update for that service is available. It gets a bit tedious with 12-15 services every couple of weeks so I need a centralized and more efficient way of “keeping up”.

Is there some type of app that can track whether an app/service has a new version available? Ideally it can send me some type of notification, self-hostable, and ideally not Portainer?

14 points

I just subscribe with RSS to the releases page on github of each project

permalink
report
reply
6 points

Thanks!

If im doing this right, the url is just the releases page for the repo with a .atom at the end. So for Vaultwarden it is https://github.com/dani-garcia/vaultwarden/releases.atom

permalink
report
parent
reply
4 points

This sounds like the simplest and most effective solution. Thanks!

permalink
report
parent
reply
12 points

GitHub has the option of emailing you on releases etc. by email.

permalink
report
reply
4 points
2 points
*

Yeah, depending on the branch I’ve found that method not to be too reliable. openrss offers branches for RSS feeds for commits on every branch though: e.g. https://openrss.org/github.com/octokit/octokit.rb/commits/main

permalink
report
parent
reply
3 points

Simple solution. I like it! Although I think it will get lost in the sea of daily emails….

permalink
report
parent
reply
10 points

RSS feeds

permalink
report
reply
5 points

Love that username tho!! Yeah might just do RSS. I already run FreshRSS and it’s ability to filter stuff would probably come in handy too

permalink
report
parent
reply
3 points

RSS notifications from their respective release pages is how I’m doing it.

permalink
report
parent
reply
5 points
*

Maybe take a look at Diun or Watchtower

I use Diun and ntfy to get push notifications about new docker image versions on my smartphone. Other options include notifications for Discord, mail, MQTT, Slack, Webhook and more.

permalink
report
reply
2 points

Was not aware of Diun, will check out!

permalink
report
parent
reply
4 points

Taking a brief look at that blog post, the author doesn’t know that wt can be set to only notify… Or that wt can be set to act at specific date or time… It’s like they never looked at the wt env variables at all, just yolo defaults and then complain that it doesn’t do what they want out of the box (‘because my settings are the best and they should clearly be the default for everyone!’). For someone who spent much time exploring other options and complaining, they didn’t take ~10 minutes to learn that the initial issue was indeed themselves.

(I use wt and set up many options to avoid these issues, successfully)

permalink
report
parent
reply
1 point

While of course Watchtower can be configured to not update and only notify there is also a nice, lightweight alternative out there that is built only for image update notifications: Diun.

I think he looked at it.

permalink
report
parent
reply
3 points
*

I use renovate myself. Via a cron job against a self hosted gitea instance.

https://github.com/renovatebot/renovate

Works for many dependency types including docker images. You can also have it pin non version tags (using digests).

permalink
report
reply

Selfhosted

!selfhosted@lemmy.world

Create post

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.

Rules:

  1. Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

Community stats

  • 4.8K

    Monthly active users

  • 3.8K

    Posts

  • 83K

    Comments