I just do this. Get email notifications for new tagged releases, check changelog, everything fine?
docker-compose pull; docker-compose down; docker-compose up -d
And we are done
Comment on Get notified on Mastodon for new Github releases
gla3dr@lemmy.ca 9 months ago
Why not just subscribe to the release notifications or use the releases atom feed?
eskuero@lemmy.fromshado.ws 9 months ago
Link@rentadrunk.org 9 months ago
You don’t need to run docker-compose down.
docker-compose pull; docker-compose up -d is enough
eskuero@lemmy.fromshado.ws 9 months ago
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 8 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 8 months ago
You can
docker compose up -d <service>to (re)create only one service from your Dockerfile
dan@upvote.au 9 months ago
FYI,
docker-compseis 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.
bjmllr@lemm.ee 9 months ago
Off the top of my head, boosting, voting, and discussion.
gla3dr@lemmy.ca 9 months ago
Yeah, good point!
ryan_harg@discuss.tchncs.de 9 months ago
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 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 9 months ago
That makes sense. Pretty cool, nice work!