I did not yet read anything about it but it’s not “highly unstable” anymore
You must log in or register to comment.
I’m running it for about a year and I never noticed any instability. To fair Android app did not always work well.
Nevertheless I never had a problem with updating it once every couple of months. Changlog and upgrade instructions always covered everything.
I’ve had Immich auto updating alongside around 36 other docker containers for at least a year now. I’ve very very rarely had issues, and just attach specific version tags to the things that have caused problems. Redis and postgres for example in both Immich and Paperless-NGX have fixed version tags because they take manual work to upgrade the old databases. The main projects though, have always auto updated just fine for me.
The reason I don’t really worry about it: Solid backups.
BorgBackup runs in the early AM, shortly before Watchtower updates almost all of my containers, making a backup of the entire system (not including bulk storage) first.
If I was to get up in the morning and find a service isn’t responding (Uptime-kuma notifies me via email if it can’t reach any container or service), I’ll mess with it and try to get the update working (I’ve only actually had to do this once so far, the rest has updated smoothly). Failing that, I can just extract yesterday’s data from the most recent backup and restore a previous version.
Because of Borgs compression and de-duplication, concurrent backups of the same system can be stored in an absurdly small amount of space. I currently have 22 backups of ~532gb each, going back a full year. They are stored in 474gb of disc space. Raw, that’d be 11.8TB
Exactly this, I have hourly Borg backups and also since my install is entirely on a zfs array I have zfs autosnapshot every 5 mins with retention policy. Takes almost zero cpu or memory overhead extra and means and can do just about anything via command line and revert it back with ease.
That being said, I still don’t auto update. Unless having an issue, I just sit down every few months and update everything manually because if its already working why update. If you want the newest features, how will you even know what they are if you don’t at least glance at the release notes?
Alright, you just sold me on borg backup. Well done.
This is why I switched to ZFS with sanoid+ syncoid. Any breaking update or data corruption can be rolled back, giving you the freedom to auto-update with minimal risk.
You will never know when breaking changes will happen, that’s why I wouldn’t recommend an auto update.
But that’s why we have semantic versioning. Automatically apply minor versions and fixes, but notify for major versions.
Immich obviously does not follow semantic versioning when 2.0 is to be considered the first stable version.
Or you can be a happy user, as it is using semver since version 2.0.0
Luckily they are on 2.0.1 now so there has been 2 stable version by now
INHO never auto-upgrade anything.
Leave it a day / week or so, and then manually upgrade.
(And do a backup of application database(s) first.)
