Immich 2.1 Released with Better Slideshow Shuffle, New Notifications
Immich 2.1 Released with Better Slideshow Shuffle, New Notifications
linuxiac.com
Immich 2.1 Released with Better Slideshow Shuffle, New Notifications
Comments
60-
-
I’m finally migrating from iCloud Photos to Immich next weekend. I finally have my NAS setup going
-
Can you please let us know how the transition went after a few weeks? I’m also considering the same but I’m also content with Apple Photos features like live photos etc.
-
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
-
Live Photos works in Immich.
One thing I really like about Apple photos is the memories that it suggests.
-
Live photos are supported but only in the web version as of now
-
-
-
Immich is such a cool piece of software 🤩
-
oh fuck me i missed the 2.0;-)
-
I mean, if you’re offering….
-
-
Every day that I don't switch, immich keeps getting better!
-
Do it
-
Yeah I've been waiting until it's updates stop breaking backwards compatibility. It's sounding better and better as time goes on.
-
Wait no more! Immich 2.0 is the first stable release. https://github.com/immich-app/immich/releases/tag/v2.1.0
-
-
-
I love immich and as soon as the feature for automatic clean up for already backed up images is available it’s going to be perfect.
-
automatic stacking would be nice too
-
-
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.
-
The same way as all other services: all relevant data (compose.yml and all volume mounts) are in a btrfs subvolume. Every night a snapshot gets made and mirrored to a remote server by btrbk.
-
I run Immich in a VM on Proxmox which gets backed up every 12 hours and all my photos are on the NAS which gets snapshotted every 12 hours and pushed to an external drive and a Hetzner box.
-
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 clone the dirs nightly to a separate server + storage. Monthly to an offsite.
-
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...
-
I have Immich on a proxmox container and use proxmox backup. It has already save me once.
-
Nothing fancy. I use Backrest for all my backups, and a few of my plans just include the Immich directory. My NAS is an entirely separate machine so my local backups go there, while everything is simultaneously pushed to a backblaze bucket
-
Immich photos are one of the main thing I backup. I use duplicacy and I backup to backblaze B2 storage. It does incremental backups. Same thing with docker persistent data or other things I consider important.
-
I backup the underlying storage (which is a VM) that immich writes to.
In theory it should be a perfect copy that just crashed. -
Borg backup runs every hour on all my docker folders
-
ZFS sending to a remotelab.
-
-
Has anyone be able to get memories to work. I don't get any notifications. I probably don't understand how that works. Any pointers except the official documentation will be helpful.
-
Notifications? It doesn't give you notifications. It just shows it at the top in the main interface (if there are any).
-
They show images from the same day in past years. So if your library has no images >= 1 year old I'm not sure if anything shows up.
-
-
Still crutching on containers?
-
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:
-
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
Which isn't a great idea with all the breaking changes. I'd assume it gets better after v2, but still.
This looks a lot more complicated that Watchtower. Is this something different or add other functionality?
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.