I’m not familiar with Watchtower, I assume it will restart the container/stack if a new image is found. The biggest difference is that an edit to the git repo causing the container to be redeployed. This means the git repo becomes the source of truth and its possible to redeploy even when config changes get merged.

Did you learn anything?

I’ve been doing this in my kubernetes cluster since immich was less than v1.49.0 (that’s the earliest I can find but it’s been over 4 years).

Your comment could have been more constructive: something like “this is really cool, just be sure you don’t auto merge PRs without reading the patch notes. Learn about the process before you roll this out to your mission critical systems!”

This is a learning opportunity (possibly even for you). Show others how to do things well and the whole community can benefit.

Gitops is your friend

https://nickcunningh.am/blog/how-to-automate-version-updates-for-your-self-hosted-docker-containers-with-gitea-renovate-and-komodo

The email tracking is even worse. I really hate the obfuscated links with who knows what embedded tracking. At least the ?ref is clear. It’s brought me close to unsubscribing