Comment on Immich vs Ente ?
lka1988@lemmy.dbzer0.com 3 weeks ago
Downside: breaking changes are fairly common AFAIK.
Breaking changes only come with major version changes now.
Comment on Immich vs Ente ?
lka1988@lemmy.dbzer0.com 3 weeks ago
Downside: breaking changes are fairly common AFAIK.
Breaking changes only come with major version changes now.
_Nemo_@lemmy.ml 3 weeks ago
I do still read the changelogs and compare compose files thoroughly on every major update. With that in place, Immich has not once broken down on me, and I’ve been here from almost the very start.
lka1988@lemmy.dbzer0.com 3 weeks ago
Oh, same here. As soon as I discovered Immich, I pored through all the info I could get my hands on and found that breaking changes happened often, so I made absolutely certain to read every changelog for things that may affect my setup. I sstopped updating it last year due to life getting in the way, and it was stuck on 1.138 (and shut off) until last week when I decided to pay attention to it again.
_Nemo_@lemmy.ml 3 weeks ago
I’ve got a second deployment of immich that also got stuck somewhere on v1.x. May I ask how you upgraded to the most recent version? Did you just go for 3.0, or did you do “baby steps” in between? (e.g. 1.138 > 2.0 > 3.0)
lka1988@lemmy.dbzer0.com 3 weeks ago
Pretty much that. Downloaded the latest
compose.yml, copied all the relevant bits from my existing compose file to the fresh one (volumes, database/db credentials, etc), set the version tov2.0.0, and let 'er rip. Made sure it was playing nice, then checked all the changelogs up to 2.7.x (whatever patch was the newest last week), set the version tov2, and updated it again.Fast forward to this week, all I did was set the version to ‘v3’ and the update took without a problem.