156
Immich v1.109.1 released with optional paid license
(github.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 18 Jul 2024
156 points (97.0% liked)
Selfhosted
40767 readers
1625 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
I don't mind this model. That being said for me Immich is great but has a fatal flaw that has prevented me from using it: it doesn't do updates.
For me that's a big one, everything else I self host I have a docker compose pointing to latest, so eventually I do a pull and up and I'm done, running the latest version of the thing. In Immich this is not possible, I discovered the hard way that they are not backwards compatible and that if you do that you need to keep track of their release notes to know what you need to manually do to update.
I haven't settled on a self-hosted photo management because of this. In theory Immich has almost everything I want (or more specifically, all of the other solutions I found lack something), but having to keep track of releases to do manual upgrades is stupid, this is a software, it should be easy to have it check the version on start and perform migration tasks if needed.
This just means that this project is still too early in development for you. The breaking changes happening in this phase are going to pay off in the long run and prevent the project from getting bogged down.
I would give it another shot when they release v2
Yeah, I have high hopes for the project, it ticks almost every box for me. I would still prefer to be able to store tags in the actual images and use them and also be able to recover a library already in the proper folder (so in the case of a catastrophic failure, reimporting the full library is a matter of minutes not days, not to mention having to retag people, etc).
My point is that projects should ask for donations when they're so early in development, asking for a subscription implies you have a stable product.
This is not a subscription but a perpetual license and for my needs it’s already well worth the price they are asking. Using this actively with my wife but also sharing albums with about 8 other family members.
I find the no-subscription model very attractive and I’m open minded to companies trying out new software licensing approaches. I like the idea of the developers getting paid for their good work and being able to do it full time.
Yeah, I am very very tempted to go for it, mainly because it is not a subscription. I wish it would have been less than $100 though, but I am not arguing about that since whatever I feel I would want to pay is probably less than they would think is OK.
That's the thing, if the project is too early to have a stable enough structure to allow for programatical updates then it's probably too early to offer something "perpetual"
Having everything on latest seems a very bad idea.
Why? Latest means latest stable for most services
Latest also means automatic major upgrades without doing the steps necessary for said upgrade, or breaking functionality/changes.
See: https://medium.com/@mccode/the-misunderstood-docker-tag-latest-af3babfd6375
https://vsupalov.com/docker-latest-tag/
https://cloudmaniac.net/docker-container-never-use-latest-cicd-pipeline/
That's interesting, although most of it is directed at people building the images, the fact that pushing without a tag sets the latest is something I did not know and something that I could see the human factor causing a problem.
Well, they do say, that it is in very active development. There will be a time when updates get more stable and where they will offer an automated update path, just not now.
Yup, and I'm fine with that, but I think that switching from a donation to a subscription model before then is wrong.
I mean... It's perfectly usable as it is. Even though it's still in early development, it already has more feature than basically every competitor (except Google Photos maybe)
I agree, I'm not trying to bad mouth the project, I just feel that they shouldn't change from a donation structure until they have a stable version of the product.
But this is not a subscription yet. Its a lifetime license. Of course they might change terms, you never know.
No need to update unless they're is a feature or security patch.
Updating to latest could result in not knowing your version in case of recovery or have an exploit pushed.