Unfortunately this occurred at the exact moment I was deploying some changes. Makes me think that being so dependent on GitHub for a production code repo is a little big dangerous. Redundancy would certainly solve this issue, though.
[deleted]
GitHub was down
11–20 of 30 posts
Re: GitHub was down
#12Guys, please don't forget the advantage of using DVCS to begin with. I like Github too, but if Github goes down it shouldn't put the brakes on your work. Push to multiple remotes. Solved.
Re: GitHub was down
#13Guys, please don't forget the advantage of using DVCS to begin with. I like Github too, but if Github goes down it shouldn't put the brakes on your work. Push to multiple remotes. Solved.
[deleted]
Re: GitHub was down
#14Guys, please don't forget the advantage of using DVCS to begin with. I like Github too, but if Github goes down it shouldn't put the brakes on your work. Push to multiple remotes. Solved.
A lot of people rely on other features of GitHub for their workflow: issues, pull requests, comments.
Re: GitHub was down
#15Genuine question – who DDoSes Github? From what I've seen, DDoS attacks often seem to be a response to a site or company entering the political sphere in a controversial way.
In previous threads about Github being DDoS'd, I asked the same question. Apparently it's some scheme to ask ransom from companies/startups that have enough money to pay and/or not enough infrastructure to sustain the attack without giving up.
Yep. There's a well-written article about an early DDoS extortion attempt where the victim fought instead of paying, developing some novel protection technology in the proces: http://www.csoonline.com/article/print/220336
Re: GitHub was down
#16Unfortunately this occurred at the exact moment I was deploying some changes. Makes me think that being so dependent on GitHub for a production code repo is a little big dangerous. Redundancy would certainly solve this issue, though.
There's already built-in redundancy. Wherever you pushed to Github from has a complete copy of the current state of your repository. Github is effectively just a publicly accessible mirror, but you can always push to a different remote elsewhere, push directly to your production instance, or even host your repo in an s3 bucket, all while Github is down.
Re: GitHub was down
#17Guys, please don't forget the advantage of using DVCS to begin with. I like Github too, but if Github goes down it shouldn't put the brakes on your work. Push to multiple remotes. Solved.
A lot of people rely on other features of GitHub for their workflow: issues, pull requests, comments.
I've been telling people for a fair while that I wish Github issues were stored as part of the git repos themselves, not so much for availability reasons as that it'd be awesome if the state of bugs got branched and merged along with everything else, so that a bug could be fixed in a branch, but not yet in master, and would get fixed in master when the branch got merged. But I guess availability would be a nice additional perk.
Re: GitHub was down
#18Earlier quoted context omitted.
A lot of people rely on other features of GitHub for their workflow: issues, pull requests, comments.
I've been telling people for a fair while that I wish Github issues were stored as part of the git repos themselves, not so much for availability reasons as that it'd be awesome if the state of bugs got branched and merged along with everything else, so that a bug could be fixed in a branch, but not yet in master, and would get fixed in master when the branch got merged. But I guess availability would be a nice addit…
You're welcome: http://bugseverywhere.org/
Re: GitHub was down
#19Earlier quoted context omitted.
A lot of people rely on other features of GitHub for their workflow: issues, pull requests, comments.
I've been telling people for a fair while that I wish Github issues were stored as part of the git repos themselves, not so much for availability reasons as that it'd be awesome if the state of bugs got branched and merged along with everything else, so that a bug could be fixed in a branch, but not yet in master, and would get fixed in master when the branch got merged. But I guess availability would be a nice addit…
What I would like to see is an analogue to offlineimap for GitHub's project management services.
The protocol could even be email based.
e.g. a pull request is an email with the git formatted patch attached. Issues are emails with discussions as threaded mail/news, etc.
Re: GitHub was down
#20Earlier quoted context omitted.
I've been telling people for a fair while that I wish Github issues were stored as part of the git repos themselves, not so much for availability reasons as that it'd be awesome if the state of bugs got branched and merged along with everything else, so that a bug could be fixed in a branch, but not yet in master, and would get fixed in master when the branch got merged. But I guess availability would be a nice addit…
You're welcome: http://bugseverywhere.org/
Wow, slick. Thanks for sharing.