I have Immich Server Version: v1.115.0. They’re up to v1.129.0. I am guessing there have been lots of breaking changes in that range, since that was true the last time I updated.
Is there a safe way now to update without making me read all the release notes and carefully craft my docker compose file in multiple steps to make sure I don’t lose anything in the process of getting caught up?
Thanks for any tips.
ETA: Or just, how do you handle your Immich (in Docker) updates in general?
2ND EDIT: I did read the release notes. After a lot of reading, there was 1 change (updating their internal Port # for the main service to 2283) It’s done. Thanks y’all. My cats appreciate you all.
I’d take a backup, first, and then just send it. Then, if that doesn’t work out, do it the hard and slow way.
I just had to do this. Don’t skip the release notes. They’re really good at highlighting potential pitfalls, just scroll back through and look for the heading “Breaking Changes.”
In my case there were a few, but they were only for API calls I’m not using, so I just did the update in one go and it worked out great. (Of course, I made sure to take a backup first.)
I neglected to update for like seven “major” versions recently. I took the safe-ish route to just read every release note as I go and install the last minor version of each major version release, then start, quick check, stop, next one. It turned out fine.
edit: Backup, backup, backup. Then you can’t fail.
Good opportunity to test your backups.
Restore to a new directory, update that and see what happens. If it works do it to the original.
Yum-cron is the way.
Maybe immich will see the way.
Yum-cron
Hmmm, I’ve heard some people use watchtower too.
You’re going to have to read every single release with breaking changes.
That’s one of the reasons I favour Semantic Versioning…
Don’t trust Semantic Versioning claims, devs can and so screw it up. That said, if they claim to follow semver, it’ll probably work, but I’ve had patch versions break my code before.