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
I have never been a fan of anything above 3 nines of uptime even in a business situation.
Your business will not collapse because of 10 min of downtime a week, and if it does that is not technologies fault.
I don't even bother to track my home setup.
I found the GitHub employee! π
There are plentiful scenarios where 10 minutes of sequential downtime would be a critical issue. Say you're a telecoms or internet provider - even a one minute delay to a life-saving message can be enough for someone to die.
Furthermore, lots of things are interconnected now. Your business might be able to handle 10 minutes of downtime, but lets say my business relies on 12 different service providers like you, who each have 10 minutes of downtime during a week using your rationale. That could up being 2hrs of downtime each week.
99.999% is about 5 minutes and 16 seconds of downtime per year.
12 services down perfectly sequentially works out to 76 minutes per year, not 2hours per week.
Not saying there aren't applications where that can't be catastrophic, but you're scale is off for three 9 downtime.
His comment was not based on three nines, the OP is the one that brought up 10 min a week
Yes, there are some that do, I should have said that. But the number of orgs that need extreme uptime is so small compared to business that think they do need it but really don't.
My home server is 100% up, because I never check it and that's how it works, right?
I didn't turn it down, so it's obviously up.
SchrΓΆdingers home server
Hospitals? Air traffic control? Power grid operators? Like these are exceptional businesses, but they're out there.
I agree, but the number of business that have actual need for extreme uptime is insignificant compared to the number of businesses that don't but think for some stupid reason they do.
Many airports are closed at night.
Good point, but that's planned downtime.
Those do actually go down. Hospitals have to be evacuated after an earthquake, airports force all aircraft to divert or the grid has the sort of outage that gets it's own Wikipedia page and needs to be black started.
That's the point I'm making: when those examples go down unplanned, in particular hospitals and the power grid, in particular the examples you gave, those can be catastrophic events. I.e., if we ignore planned downtime, then these businesses really need five lines of reliability during the times they are expected to be up.
I agree with the overall point that the average business doesn't need five nines of availability, but I wanted to point out that there are definitely businesses that do.
I host home assistant and if anything goes down I'll notice pretty fast.