Selfhosted

43945 readers

451 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

[Resolved] How to update Immich now that I am way behind? (lemm.ee)

submitted 1 day ago* (last edited 1 day ago) by perishthethought@lemm.ee to c/selfhosted@lemmy.world

19 comments fedilink hide all child comments

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.

collapsed inline media

you are viewing a single comment's thread
view the rest of the comments

[–] sugar_in_your_tea@sh.itjust.works 5 points 1 day ago (1 children)

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.

[–] moroni@lemmy.ca 2 points 11 hours ago (1 children)

That's true, but it applies to any versioning system. If they're not following semver and just mentioning breaking changes in their changelog, we'll inevitably run into situations where developers make mistakes.

[–] sugar_in_your_tea@sh.itjust.works 1 points 7 hours ago

Yup. As always, do backups for anything important. Semver is certainly helpful in communicating scope of changes.