Live data from Hacker News

GitHub - Major Service Outage

status.github.com

31–37 of 37 posts

Re: GitHub - Major Service Outage

#31

just out of curiosity, does anyone find these HN postings useful? wouldn't your critical shit break long before you go read about it on HN? otherwise, why not just rely on their human-friendly status pages that get served if such a thing occurs? i don't understand why this is on the front page, since it's not an infrequent occurrence.

Also the posting comments become a 'place' to put suggestions, alternatives, and other measures to deal with the issue.

Re: GitHub - Major Service Outage

#32
I think someone should write a tutorial about how to continue working while Github goes down. If you're trying to deploy from a master branch on GitHub, this could be an issue, but if you're just trying to share projects between peers, this should be a that big of a deal right?

Re: GitHub - Major Service Outage

#34
post #32

I think someone should write a tutorial about how to continue working while Github goes down. If you're trying to deploy from a master branch on GitHub, this could be an issue, but if you're just trying to share projects between peers, this should be a that big of a deal right?

We found out the hard way that directly deploying from github might be a bad idea. I wrote a little web service that receives notifications via hooks when code is tagged and rehosts the tarballs in S3 for deployment. it's been rock solid in production.

Re: GitHub - Major Service Outage

#35
post #27

just out of curiosity, does anyone find these HN postings useful? wouldn't your critical shit break long before you go read about it on HN? otherwise, why not just rely on their human-friendly status pages that get served if such a thing occurs? i don't understand why this is on the front page, since it's not an infrequent occurrence.

There is a reliable indicator of whether or not people found the post useful - the number of points the submission has. To be honest, I find comments like yours far less useful, and they are not infrequent either.

i find this indicator not to be consistently reliable. anything that gets to the front page (which will never be pure crap), will always get upvotes.

but many (all?) submissions that make it to the front page get there by being manually curated there, not by accumulating upvotes first. on the flip side of the same coin, a lot of good things never make it to the front page, even if they gain a lot of points.

Re: GitHub - Major Service Outage

#36
post #31

just out of curiosity, does anyone find these HN postings useful? wouldn't your critical shit break long before you go read about it on HN? otherwise, why not just rely on their human-friendly status pages that get served if such a thing occurs? i don't understand why this is on the front page, since it's not an infrequent occurrence.

Also the posting comments become a 'place' to put suggestions, alternatives, and other measures to deal with the issue.

this is valid, though for stuff that occurs so frequently there should just be a sticky that can accumulate suggestions, not a clean slate submission for every time it happens.

Re: GitHub - Major Service Outage

#37

Earlier quoted context omitted.

Github's awesome, but yah, that's the downside of having one place that hosts so much code. Having some outage or disruption is feeling like a bi-weekly event..

"bi-weekly"... Do you mean twice a week or fortnightly?

> "bi-weekly"... Do you mean twice a week or fortnightly?

On a previous team we developed the mental image of a bicycle, consisting of two cycles.

It seemed to help at the time.. but now I think about it I'm not sure how it did!

Post reply on HN