Live data from Hacker News

GitHub Down with a 503

status.github.com

21–30 of 89 posts

Re: GitHub Down with a 503

#24
post #13

Right in the middle of a major push to production. Awesome.

It's too bad git requires a central server.

How is this a useful comment? Everybody knows that Git is distributed. Everytime Github's down, somebody feels the urge to remind everybody else about that.

Github's not only Git. Lots of services integrate with Github. Stuff like continuous integration, continuous deployment. If your system is built on those things, Github being down will prevent you from deploying.

What's the alternative, replicate everything in-house/self hosted? Should startup stop using third party service providers?

Re: GitHub Down with a 503

#25
post #9

Haha, I wonder how many of us came here because we couldn't push or pull commits, so just taking a HN reading break... and boom the top post is about Github!

When Github appears down, I come to HN to find out if it's affecting everyone :p

Re: GitHub Down with a 503

#28
post #25
post #9

Haha, I wonder how many of us came here because we couldn't push or pull commits, so just taking a HN reading break... and boom the top post is about Github!

When Github appears down, I come to HN to find out if it's affecting everyone :p

'Gee, github is down. Is it just me? Better check HN!' Exactly what I just did too.

Re: GitHub Down with a 503

#30
post #13

Earlier quoted context omitted.

It's too bad git requires a central server.

How is this a useful comment? Everybody knows that Git is distributed. Everytime Github's down, somebody feels the urge to remind everybody else about that. Github's not only Git. Lots of services integrate with Github. Stuff like continuous integration, continuous deployment. If your system is built on those things, Github being down will prevent you from deploying. What's the alternative, replicate everything in-ho…

If your workflow involves services that integrate with GitHub, you should have a plan for when GitHub is not available. You've got your source code elsewhere, you should have docs and procedures for running the tests in your own dev environments and for utilizing whatever staging/deploy process you prefer without GitHub as an intermediary.

I continue to post comments like that because while I love GitHub, watching the community put all their eggs in GitHub's basket, especially when GitHub lives on top of a tool designed to avoid SPoFs, is concerning.

Post reply on HN