this post was submitted on 31 Jul 2023
16 points (94.4% liked)

Selfhosted

40132 readers
557 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

I’ve seen a lot of recommends for Immich on here, so I have an idea what the answer here is going to be, but I’m looking for some comparisons between it and Photoprism I’m currently using Synology Photos, and I think my biggest issue is it’s lack of metadata management. I’ve gotten around that with MetaImage and NeoFinder. I’m considering moving to something not tied to the Synology environment.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 0 points 1 year ago (1 children)

I've been using Photoprism for a while, but found it very resource-heavy for my poor little NAS. Even after finishing ingesting my photo library, and finished tagging all the faces, it still occupies about 50% CPU routinely. However, I can't install Immich because apparently the CPU on my NAS doesn't support AVX required by typesense.. Anyone know of some work-around?

[–] [email protected] 1 points 1 year ago

For now you could remove Typesense from the Docker image. Just edit the .env and remove the # in # TYPESENSE_ENABLED=false

Then go to the Dockerfile and comment out the Typesense service.