this post was submitted on 15 Feb 2024
72 points (92.9% liked)

Selfhosted

40329 readers
380 users here now

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!

founded 1 year ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
72
Get notified on Mastodon for new Github releases (codeberg.org)
submitted 9 months ago* (last edited 9 months ago) by ryan_harg@discuss.tchncs.de to c/selfhosted@lemmy.world
23 comments fedilink hide all child comments
 

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?

you are viewing a single comment's thread
view the rest of the comments
[–] gla3dr@lemmy.ca 25 points 9 months ago (6 children)

Why not just subscribe to the release notifications or use the releases atom feed?

[–] BlackEco@lemmy.blackeco.com 10 points 9 months ago (1 children)

Exactly, I don't get the "Mastodon as a poor man's RSS agregator" trend

[–] gla3dr@lemmy.ca 3 points 9 months ago

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.

[–] eskuero@lemmy.fromshado.ws 8 points 9 months ago* (last edited 9 months ago) (3 children)

I do it that way. Enable email notifications for new tagged releases, something arrives, check changelog, everything fine?

docker-compose pull; docker-compose down; docker-compose up -d

And we are done

[–] Link@rentadrunk.org 2 points 9 months ago (1 children)

You don’t need to run docker-compose down.

docker-compose pull; docker-compose up -d is enough

[–] eskuero@lemmy.fromshado.ws 1 points 9 months ago (2 children)

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

[–] Link@rentadrunk.org 2 points 9 months ago

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.

[–] 7Sea_Sailor@lemmy.dbzer0.com 0 points 9 months ago

You can docker compose up -d <service> to (re)create only one service from your Dockerfile

[–] dan@upvote.au 1 points 9 months ago* (last edited 9 months ago)

FYI, docker-compose is 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.

[–] ryan_harg@discuss.tchncs.de 7 points 9 months ago* (last edited 9 months ago) (1 children)

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.

[–] gla3dr@lemmy.ca 1 points 9 months ago

That makes sense. Pretty cool, nice work!

[–] bjmllr@lemm.ee 2 points 9 months ago (1 children)

Off the top of my head, boosting, voting, and discussion.

[–] gla3dr@lemmy.ca 1 points 9 months ago

Yeah, good point!