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
Good points. For the hardware, there are additional things I'd like to self host (personal website, media server, game servers, etc.) so I was imagining hardware I could grow into. I have a trial setup (git, lemmy, and apostrophe CMS managed by portainer + nginx + Heimdall) on my gaming pc that seems to work well and which I'd like to make a permanent version of. Definitely not married to having a blade, but I definitely want to go on premises. If there's downtime, it'll be because of an internet/power outage affecting the neighborhood, so no one'll be trying to access it anyway. Adoption will be hard either way (the people I live around are mired in the metaverse ๐ญ) and I'm open to suggestions on that as well.
Wouldn't they especially want a working communication channel in case there is an extended power outage?
If you want it to be an actual community service, then you want it to be something that outlives your residence, your tenure as event coordinator, and your interest in being the neighborhood IT guy. It'll be much easier to transfer control of a VPS to your successor than to give them hardware that also hosts a bunch of your personal services.
You can start with a very small, nearly free VPS while you recruit users & scale up as (if) anyone bites. Probably even get the HOA to pay for it.
Very wise, consider me convinced