Because you point to :latest and everything is dockerized and on one machine? How does it know when it’s time to upgrade?

Yeah, For some reason I didn’t think of ansible even though I use it at work regularly. Thanks for pointing it out!

So everything is dockerized and points to :latest?

What about the necessary changes to the docker compose files? What about changes necessary in nginx configs?

I guess you also read each release notes manually?

I am developing a script which will do that specifically for my services.

Right now at the first stage it only checks GitHub, Codeberg, etc. To check if there is a new version compared to what each service is running right now.

https://git.jeena.net/jeena/service-update-alerts

I am extending it now with a auto update part, but it’s difficult because sometimes I can’t just call a static script because some other migration things need to run. So I have a classifier which takes the release notes and let’s a local LLM to judge if it’s OK to run the automation or if I need to do it manually. But for that I am collecting old release notes as examples from each service. This takes forever to do so I only have it done for PieFed, PeerTube, Immich and open-webui, and I didn’t push those changes to the public repo yet.

Hm, I didn’t think of ansible, that’s something I should think about to use.

What is n8n?