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: 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:
- 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
Well, a fault isn't just an outage.
You said the other person involved isn't technical: what if say, a database corrupts itself and you're on vacation for a week.
Is the expectation that you'll always be available all the time to fix technical problems?
And, as a failure state: what happens if you simply cannot be reached for that week no matter what. What's the failover plan for the rest of the people involved in the business?
Yeah, the bus factor is an issue to take into account also. I'll need to find someone else to be able to solve those issues.
And then you are basically hiring an infra team to run the services and have the redundancy, and then with salaries you're nearing just paying for software again