Selfhosted
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.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.
-
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post.
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!
view the rest of the comments
As an FYI to people who are upgrading and use a preexisting postgres database If you still use pgvectors.rs (if the command \dx on the immich database responds with vectors not vector) you will need to install both pgvector and vectorchord in order to continue using immich. This will require restarting your postgres instance at least once if not twice.
It threw me for a loop at first because of the similar naming. Just thought I would share.
Isnt that only relevant to users that started with a very old setup guide?
I started in the still-beta stage (I'd say 20-30 updates before the 1.0.0 release) and already had the immich version of the postgre vector container in the compose template.
I'm not sure, I was running 2.7.5 myself but i am not sure what version of immich I started with. I don't think this would effect fully docker setups much anyway. I think this would mostly effected people who had configured with a preexisting database. I believe the docker edition with postgres built in upgraded for you awhile back unless you supplied an environment variable telling it to do otherwise.
Make sure you take a backup. Changing the docker container nuked my db. Had to restore from a backup