Immich 2.1 Released with Better Slideshow Shuffle, New Notifications
Immich 2.1 Released with Better Slideshow Shuffle, New Notifications
I transitioned from Google photos to immich about a year ago:
face recognition is absurdly much better
searching for images is some black magic stuff
it’s generally faster
it’s map is really slow
Huh? The map isnt slow?
How many geotagged pictures do you have?
Live Photos works in Immich.
One thing I really like about Apple photos is the memories that it suggests.
Gitops is your friend

In this guide I will go over how to automatically search for and be notified of updates for container images every night using Renovate, apply those updates by merging pull requests for them in Gitea, and automatically redeploy the updated containers using Komodo.
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)
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.
I use rsync to backup, I can delete and restore the whole drive if i want at any time.
I use watchtower to keep things updated. If you schedule the rsync and watchtower correctly, you can get the backup done before the upgrade and there’s basically no lost data with the rollback.
I use uptime Kuma for monitoring, and it shoots me an email with details on what failed.
The 2.0 release resolves a large amount of technical debt and shifts the focus toward compatibility and easier upgrades.
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.
Why this complicated setup? Komodo handles auto update by itself. It also update the whole stack at once, so no shutdown of the BD while the app stays up. Just have 2 checkboxes to tick.
The less stuff the better, it’s essential in case you have a failure. I only have to redeploy komodo, then all my stacks will be ready to get back online. I even removed watchtower.
I hated them too at first, but that’s because I didn’t understand them and they were new and scary.
They’re still a little scary but, after having a dependency issue on another Linux box, I get the purpose of docker a little bit better now.
Here’s a helpful primer:
Those who run immich, how have you been backing up your library?
My deployment isn’t anything fancy, it is currently a Raspberry Pi 4 with a 2TB external drive for the photo library. Been running for more than 6 months with minimal issues. Now that we are at a stable release I need to get some kinda backup going for the photos themselves.
Translation: “I run immich in a virtual machine, which I can manage from a web browser. The photos themselves are stored on a different device which gets backed up to a remote location twice a day.”
So why run immich in a virtual machine instead of in, say, a docker? Wouldn’t that be way less overhead? (Or is immich the only thing you’re hosting?)
I run it baremetal, the photos / videos are all on a separate location (so are “Externsl Libraries” in Immich) and are backed up…
As far as the Immich application itself, I’m not currently backing up anything as I’ve been trialing it… but, I’ll aim to backup any configurations, but I’m thinking to maybe ignore any database - it can just relearn everything if I need to do a restore… depends how big that DB is…