GitHub - Major Service Outage
11–20 of 37 posts
Re: GitHub - Major Service Outage
#12Re: GitHub - Major Service Outage
#13Re: GitHub - Major Service Outage
#14Re: GitHub - Major Service Outage
#15Major bummer when all of those open source projects go offline.. Does anybody do a mirror of github, either http or git-only?
Re: GitHub - Major Service Outage
#16wouldn'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.
Re: GitHub - Major Service Outage
#17Well this isn't good. Our integration server runs an npm install which includes a ton of dependencies that are github URLs. I guess tying our integration/deployment step to github isn't such a good idea after all.
Re: GitHub - Major Service Outage
#18https://code.google.com/p/gittorrent/
For a variety of reasons.
Re: GitHub - Major Service Outage
#19Well this isn't good. Our integration server runs an npm install which includes a ton of dependencies that are github URLs. I guess tying our integration/deployment step to github isn't such a good idea after all.
I'd suggest a rule of thumb where a build ought to be able to complete without any resources that you don't control the uptime of. As the number of such resources increases, the amount of time the build can not actually be built will tend towards 100%. A git caching proxy would be great for that sort of thing. A generic DVCS proxy would be even better.
Re: GitHub - Major Service Outage
#20ooops?