Get notified on Mastodon for new Github releases
I'm selfhosting several services, mostly based on docker containers. Many of these are managed on Github and publish releases there. What annoys me is that I regularly miss updates.
I'm also quite active on Mastodon so I thought it would be handy to have a bot automatically scanning for new github releases and posting a new toot for every new release.
The bot can be configured to scan multiple different github repositories and publish to different mastodon accounts.
I have set up accounts for:
https://mastodon.social/@navidrome_releases
https://mastodon.social/@vaultwarden_releases
https://mastodon.social/@dockerpihole_releases
https://mastodon.social/@tempo_releases
https://mastodon.social/@unifidocker_releases
You can use the notification feature of Mastodon to get a notification, whenever a new post is published. Just follow an account and hit the little bell icon on its profile page.
Here's the code, if someone is interested in that:
https://codeberg.org/ryan_harg/github-releases-bot
Is this something that you people find useful? Which other services would you like to see covered in that way?
Why not just subscribe to the release notifications or use the releases atom feed?
The bot consumes the atom feed of a repository, but I don't use a feed reader. you could also just let Github notify you for new releases. But I don't pay much attention to github notifications either. I'm a lot more likely to notice something like that if it's integrated into my social media consumption.
That makes sense. Pretty cool, nice work!
Exactly, I don't get the "Mastodon as a poor man's RSS agregator" trend
I wasn't trying to throw shade here. I was just genuinely curious about OPs motivations for doing this. It's totally reasonable that they could have a use case where this solution makes the most sense.
I do it that way. Enable email notifications for new tagged releases, something arrives, check changelog, everything fine?
And we are done
You don’t need to run docker-compose down.
docker-compose pull; docker-compose up -d is enough
I guess that's fair for single service composes but I don't really trust composes with multiple services to gracefully handle only recreating one of the containers
If only one container has been updated then when you run docker compose up -d it will only recreate that container, unless it is a dependency of another container (like a database) in which case it will restart all containers that depend on it as well.
You can
docker compose up -dto (re)create only one service from your DockerfileFYI,
docker-composeis the legacy version that was deprecated a few years ago and no longer receives updates.docker compose(with a space instead of a hyphen) is what you should be using these days.Off the top of my head, boosting, voting, and discussion.
Yeah, good point!