Github is down
21–26 of 26 posts
Re: Github is down
#22This has probably been asked in one of the hundreds "GitHub is down" posts in the last few months, but what are the alternatives (apart from bitbucket)?
Re: Github is down
#23This has probably been asked in one of the hundreds "GitHub is down" posts in the last few months, but what are the alternatives (apart from bitbucket)?
git on dropbox? (what I use, it has the feature of syncing everyones origin automatically oppertunistically) http://edinburghhacklab.com/2012/11/easy-version-control-git...
Maybe I'm overly risk-averse, but I've been bitten a few times by Git setups that are non-standard or complicated and decided that it's far better to keep things as simple as possible. I'm not really interested in fiddling about keeping Git running smoothly, when it's incidental to the real work. It's just not worth it to save a few bucks, versus hosting a Git repo yourself on a VPS or something.
Re: Github is down
#24Re: Github is down
#25Looks like another DoS attack: "0:18 UTC GitHub.com is recovering at this time from a DoS attack. We're continuing to monitor things and will provide further updates as the situation develops." Is there really no way to protect from these attacks!?
There is a way. Have more bandwidth then your attacker. DDoS protection services exist that forward the good traffic on to you, and they do this by having excessively large amounts of bandwidth. They also cost obscene amounts of money.
(disclaimer: I'm a google employee, but not on the page speed service).
[1] https://developers.google.com/speed/pagespeed/service/faq#mo...
[2] https://developers.google.com/speed/pagespeed/service/pricin...
Re: Github is down
#26Earlier quoted context omitted.
git on dropbox? (what I use, it has the feature of syncing everyones origin automatically oppertunistically) http://edinburghhacklab.com/2012/11/easy-version-control-git...
Props to you for actually testing simultaneous pushes where conflicts arise at the Dropbox-level, but I would still never do this (for a multiuser repo, for a single user it's probably fine). Maybe I'm overly risk-averse, but I've been bitten a few times by Git setups that are non-standard or complicated and decided that it's far better to keep things as simple as possible. I'm not really interested in fiddling about…