That may not be the right terminology. I men it's decrypted when booting and encrypted when it's unplugged or shut off.

Haha I had a much harder time with the compose formatting than I did with the actual upgrade.

Line

Or

Line.?

Either way fuck you compose. Haha

I'm super basic backup wise.

I run a rsync command that backs up the database dump and all the immich assets to a USB hdd. I do that every couple of days or when I think about it haha

I then back that USB drive up to another USB drive on my personal computer.

These drives are wd Reds and in USB enclosure.

My buddy has offered to host a off site backup but I have a toddler and as such 0 time.

I probably should look into some cold storage or something but shits expensive these days and I'm currently satisfied with where I am.

Knocks on wood

Additional context... I'm running Debian with mergerfs across like 8 drives. So my photos are spread across several drives in my /storage/photos folder. So In oder to lose everything all at once. It would have to be a flood or house fire or something..

Immich is great. I run a small friends and family instance on a NAS and I’ve never had a hiccup that took more than ten minutes to fix. My backup system is borg to a Hetzner storage box nightly with a healthchecks.io check set to email me if it goes more than 48 hours without a success. Cheap, reliable, and fast enough for me.

V3 is stable. It is the new version after V2. V1 was where the majoriry of the breaking changes happened.

Is that something you're looking for? As a practical matter, the effort to maintain multiple release branches and backports -- compared to the norm of just maintaining a single main branch -- is an outsized effort, available to only well-funded FOSS projects, usually by having an industry sponsor that makes it a priority.

I posit that the grand majority of selfhosted FOSS software, by project count, do not have back ported branches. And so production environments will want to set up an offline validation setup to evaluate update, prior to making the switch. Not convenient, sure, but not exactly insurmountable either.

At some point, some amount of responsibility for use of FOSS software must fall upon the users, or else the project is less about creating value by building up the commons for software, and more on the exploitation/abuse of the volunteers.

Some of the GUI functions for user management are paywalled. Its nothing I've found to be problematic in my use case.