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

!lsd@lemmy.world

I’m not using immich in docker. Can you explain what this breaking is there to fix?

Personally I’ve used traefik, Nginx and caddy. They’re all interesting in their own ways. My little docker setup is currently using caddy-docker-proxy. It’s been set and forget for me. You might need some adjustments based on your TLS requirements etc.

Have you shared pics of it before? I’d like to see

Holy shit that’s beautiful. Do you have one?

I can never remember the order and I’m using Wefwef which doesn’t offer markdown insert. Thanks :)

They have a page in the repo describing some advantages https://github.com/rustic-rs/rustic/blob/main/docs/comparison-restic.md