Immich 2.1 self-hosted photo and video management solution refines slideshow shuffling, adds album notifications, and polishes performance across platforms.
I’ve been running this setup for a few months now and haven’t looked back. Works super well, and essentially acts as an approval process for letting a container update or not.
The author also recently added a followup article to this one for using Forgejo instead, made migrating the setup super easy.
Your comment is spreading false information. With the stable release the Immich team has committed to no breaking changes except for major version upgrades, so if you pin to 2.x.x you will be perfectly fine
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.
This thing changes versions faster than I can update my homelab… Lol.
Gitops is your friend
https://nickcunningh.am/blog/how-to-automate-version-updates-for-your-self-hosted-docker-containers-with-gitea-renovate-and-komodo
I’ve been running this setup for a few months now and haven’t looked back. Works super well, and essentially acts as an approval process for letting a container update or not.
The author also recently added a followup article to this one for using Forgejo instead, made migrating the setup super easy.
This looks a lot more complicated that Watchtower. Is this something different or add other functionality?
Which isn’t a great idea with all the breaking changes. I’d assume it gets better after v2, but still.
Your comment is spreading false information. With the stable release the Immich team has committed to no breaking changes except for major version upgrades, so if you pin to 2.x.x you will be perfectly fine
That’s what I thought, but last time I looked I only saw a “release” tag, no “v2” tag. Did I miss something?
I automate my upgrades, but I also automate my backups, and monitoring.
If an upgrade breaks something, my health monitor lets me know and I can roll back to the previous day.
This is the way
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.
You sound condescending af.
This is a learning opportunity (possibly even for you)
Hey everyone has a learning opportunity. Some even have a separate production system!
Did you learn anything?