What do people do to get around this? Run my own git server like the good 'ol days? Github has become a central source of failure for us now...
GitHub was down
131–140 of 197 posts
Re: GitHub was down
#132What do people do to get around this? Run my own git server like the good 'ol days? Github has become a central source of failure for us now...
It was in lunchtime in New Zealand, so doesnt really matter. ;) I am just back with our world famous wellingtonian flat white, and looks everything perfect. :)
Re: GitHub was down
#133Such incidents remind me of 2 things 1. No matter what 99.99999999% availability a service provides, its utterly useless if the time to get back up is unacceptable. 2. Do not have remote services, which you cannot fully control to be a part of your run time deployments.
Uptime % includes time to recovery. Since you're not up if you're still recovering...
I think GP's point is that you should assume the 0.{however many 0s}1% it's down is going to be a bad time for you, and then ask yourself how long you want to wait to be back up.
A long down time might be worse for you than a shorter down time more frequently.
Re: GitHub was down
#134Earlier quoted context omitted.
Gitlab?
Does anyone know an alternative to githost.io? We don't want to use gitlab.org as it's painfully slow but also don't want to manage our own gitlab instance. edit: We don't like the recent changes made in githost. ( Replaced the $35 option with $149 ) We're a team of 15 people. edit2: should have clarified; I'm hooked to GitLab, just looking for another service that does managed hosting. Not looking for GitLab alterna…
Consider running your own Gitlab instance.. I run one for $40/Mo on DigitalOcean, very happy with it.
Re: GitHub was down
#135What do people do to get around this? Run my own git server like the good 'ol days? Github has become a central source of failure for us now...
At this point Github is a national security risk. The amount of passwords, keys, hashes, code, data uploaded to that system is massive. I am sure that government agencies, contractors, multinational defense departments, etc are dumping things on there hourly. Will it get hacked ? Get your popcorn out. It will happen.
Is GitHub even allowed for govt contractor use? I'd be surprised, but don't know.
Re: GitHub was down
#136Earlier quoted context omitted.
Which I can't imagine to be any more reliable than hosted GitHub. But hey, I guess there's the comfort in know that when it goes down it's our fault!
Redundancy provides availability more than reliability. The odds of GitHub going down and your local copy/instance simultaneously is very low so availability is high. Reliability is how often GitHub or your local instance goes down.
Your local instance of github and github.com are not redundant / interchangeable. If either of those goes down and you rely on it, the other one is not gonna help you much, so availability is not improved by using a local instance.
Re: GitHub was down
#137Earlier quoted context omitted.
Git is inherently distributed. There's really no reason that Github has to stand between development and production.
I think the point is git is becoming the new svn for many people.
"Becoming"? Can you point to any large project (at any point in the history of Git) that doesn't use some centralized service as a single point of distribution/source of truth?
The beauty of Git's design, though, is that you've still got everything to use it distributed even if you, under normal circumstances, just use it centralized like a fancy SVN.
Re: GitHub was down
#138What do people do to get around this? Run my own git server like the good 'ol days? Github has become a central source of failure for us now...
Your question seems to indicate that you have a runtime dependency on github. If true, this is a problem no matter where your git repo resides. You need to architect a solution wherein you do not have a runtime dependency, especially if it is a single point of failure, or accept that your reliability will never be better than the sum of your services' reli abilities (there was an article on the "calculus of availabil…
>
Your question seems to indicate that you have a runtime dependency on github.
Really he is speaking to the problem with SAAS. Sure it's cheaper to rely on someone else to do the heavy lifting for you and they can do this because they 'make it up in volume'. But the other side of that coin is no one really knows how to do that anymore. If you wanted to roll your own it's going to be very hard for your company to do the basics because you've become dependent upon the cloud, and someone else paying employees to do the basics for you... The basics have never been hard.
Re: GitHub was down
#139Earlier quoted context omitted.
Kind of? How many servers did the average app depend on in 1998? 1? Get dual HD and you were in decent shape. Compare to a modern microservice app, that maybe depends on 100 internal services and 4-5 external services. A lot of things need to go right or mostly right for things to function.
Sounds like an argument against micro services?
Only if you don't stop to consider the alternative.
Re: GitHub was down
#140Earlier quoted context omitted.
Which I can't imagine to be any more reliable than hosted GitHub. But hey, I guess there's the comfort in know that when it goes down it's our fault!
The argument is with a self-hosted solution you can choose your "danger times". If you know you have a major deliverable coming up, you can choose not to touch your git server until it's at a somewhat safe moment to do so.
While it definitely sounds like a good idea, every single time I've seen it applied, the reason was the opposite. It was essentially "we've got so little control over our stuff that we'd rather not touch". Mostly goes along with lack of backups, lack of change management, and lack of automated rebuild procedure.
If you have "danger times", then any unplanned disruption in that time will hurt so much more.