Github.com unavailable due to a large DDoS attack

Re:Github.com unavailable due to a large DDoS attack by moron4hire on Thursday October 03, 2013 @10:42AM (#6489207)

The great thing about GitHub is that it's still Git. If GitHub is down, that just means that your central publishing site is down. It doesn't mean that you're developers can't work. They can still share amongst themselves. Like they probably should be doing even when GitHub is up.

[ Parent | on HN ]

Re:Github.com unavailable due to a large DDoS attack by memset on Thursday October 03, 2013 @10:44AM (#6489223)

How would this work? (This is a serious question.)

Would each of us set up each other's internal IP addresses (192.168.0.101, etc) as remote repositories? Would each of us run a git repository on our own boxes? Or would we set one up on our own AWS box or something?

[ Parent | on HN ]

Re:Github.com unavailable due to a large DDoS attack by bigdubs on Thursday October 03, 2013 @10:48AM (#6489242)

Yep, you set up each developers machine as a remote, but you pull from them (rather than push). Helps to pull to a separate branch though.

[ Parent | on HN ]

Re:Github.com unavailable due to a large DDoS attack by moron4hire on Thursday October 03, 2013 @11:32AM (#6489617)

Well, ideally you'd have DNS setup internally so you don't have to use raw IP addresses, but essentially yes, you map each of the people with which you're collaborating as remote repositories. Because they are remote repositories, all on their own. There is nothing special between your repository on your machine and the repository on github.

[ Parent | on HN ]

Re:Github.com unavailable due to a large DDoS attack by frytaz on Thursday October 03, 2013 @10:50AM (#6489256)

Setup internal dev box, push code there and from there to github...

[ Parent | on HN ]