Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

"Major service outage"

status.github.com

Post reply on HN
Print view View original

31–40 of 60 posts

Re: "Major service outage"

#31

Post by jaequery »

PommeDeTerre wrote: post #6
templaedhel wrote: post #2

Github is great, they're working on some serious problems, and every service has downtime. But this is getting pretty serious. This is the 3rd time in these last few weeks there has been a "significant service outage" So much of a typical dev workflow is based around github, but more importantly a lot of new package managers use github as a base. Not being able to pull dependencies is a fairly big problem. I will con…

I've found it somewhat odd how, although advocating the use of a decentralized version control system, much of the git community has ended up heavily centralized on GitHub.

perhaps there maybe a way to somehow sync-up github w/ bitbucket to act as a single master origin. so we can use either or and they'll be synchronized automatically. or some company that can just act as a mirror to github would be great.

Re: "Major service outage"

#33

Post by jaequery »

snogglethorpe wrote: post #15
jeremyjh wrote: post #8

Earlier quoted context omitted.

It is a distributed system. You still have to have shared remotes in order to integrate branches.

Yup, when github barfs, you can still happily keep on hacking. You're also not limited to one shared repo by any means, so even synchronization between multiple developers can continue when github is down. To avoid problems it's of course a good idea when one of the repos is a "master", and if using a secondary repo for synchronization when the master is down, you'll probably want to switch to unique temporary branch…

well, lot of open-source projects depend on github as source of their code distribution. github is like the new sourceforge these days.

Re: "Major service outage"

#35

Post by steevdave »

jaequery wrote: post #31
PommeDeTerre wrote: post #6

Earlier quoted context omitted.

I've found it somewhat odd how, although advocating the use of a decentralized version control system, much of the git community has ended up heavily centralized on GitHub.

perhaps there maybe a way to somehow sync-up github w/ bitbucket to act as a single master origin. so we can use either or and they'll be synchronized automatically. or some company that can just act as a mirror to github would be great.

You can set git up to push to multiple repos.

Re: "Major service outage"

#36

Post by yakiv »

snogglethorpe wrote: post #15
jeremyjh wrote: post #8

Earlier quoted context omitted.

It is a distributed system. You still have to have shared remotes in order to integrate branches.

Yup, when github barfs, you can still happily keep on hacking. You're also not limited to one shared repo by any means, so even synchronization between multiple developers can continue when github is down. To avoid problems it's of course a good idea when one of the repos is a "master", and if using a secondary repo for synchronization when the master is down, you'll probably want to switch to unique temporary branch…

One possible backup would be Bitbucket (https://bitbucket.orghttps://bitbucket.org/).

(I'm not affiliated Bitbucket in any way. I don't profit from them doing well, aside from them sticking around to keep providing free hosting for me.)

Re: "Major service outage"

#37

Post by darkchasma »

templaedhel wrote: post #2

Github is great, they're working on some serious problems, and every service has downtime. But this is getting pretty serious. This is the 3rd time in these last few weeks there has been a "significant service outage" So much of a typical dev workflow is based around github, but more importantly a lot of new package managers use github as a base. Not being able to pull dependencies is a fairly big problem. I will con…

This is what I think may be their biggest problem. Because of the outages, and due to my own stupidity, I have been caught with my pants down twice because Github was always just up. And then I thought, well, lesson learned, they won't go down again, and ker-pow (I'm stupid like that).

So I have had to create a secondary remote, and for private projects, it's really easy to do so. Which is kinda problematic, because those are the accounts that keep the lights on for Github. If I have to cut budget, it's a lot more likely now that I would consider cutting the private repos.

I just hope they figure this out soon, so I can forget about how easy it was.

Re: "Major service outage"

#38

Post by hunvreus »

DigitalSea wrote: post #13

I get outages are a way of life with a widely used web application, but Github have really dropped the ball lately. This is one of many service outages lately and as a paying customer it's disheartening and worrying because I use Github in my day-to-day workflow, I and many others have come to rely on it. Don't get me wrong here, I love Github and couldn't live without it, but they really need to sort out these probl…

Github have their own datacenter and hardware, they are not relying on any cloud provider out there. It makes it harder to handle spikes of load, but they actually have an I/O intense service which justifies that choice.

Re: "Major service outage"

#39

Post by ajross »

yakiv wrote: post #36
snogglethorpe wrote: post #15

Earlier quoted context omitted.

Yup, when github barfs, you can still happily keep on hacking. You're also not limited to one shared repo by any means, so even synchronization between multiple developers can continue when github is down. To avoid problems it's of course a good idea when one of the repos is a "master", and if using a secondary repo for synchronization when the master is down, you'll probably want to switch to unique temporary branch…

One possible backup would be Bitbucket ( https://bitbucket.orghttps://bitbucket.org/ ). (I'm not affiliated Bitbucket in any way. I don't profit from them doing well, aside from them sticking around to keep providing free hosting for me.)

Another possible backup is any host on the internet. Seriously, dump it into a static file directory on any old web server or run a trivial git server. Send deltas with patch files. It's not even harder than github is, just uglier.
Post reply on HN