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. Tags [CBH] or [AIP] are required, see the links in Rule 8 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, and find example disclosures here.
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
Translation: "I run immich in a virtual machine, which I can manage from a web browser. The photos themselves are stored on a different device which gets backed up to a remote location twice a day."
So why run immich in a virtual machine instead of in, say, a docker? Wouldn't that be way less overhead? (Or is immich the only thing you're hosting?)
I have a docker VM with a gpu passed through/external access (is this called production?) and another docker VM on another machine with no passthrough/external access. So both VMs are running multiple stacks/services and i just assign based on use case. Storage and memory are cheap imo and it's the most secure way to do it with the skill level i have so it's how i run it. I'm sure there's better ways but ๐คทโโ๏ธ