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

GitHub major issues - repos have "lost" commits and site is erroring

support.github.com

Post reply on HN
Print view View original

11–20 of 91 posts

Re: GitHub major issues - repos have "lost" commits and site is erroring

#11

Post by ChuckN »

windsurfer wrote: post #7
rabidsnail wrote: post #4

Is it just me or has guthub's performance and reliability been getting progressively worse over the past month or two? Even putting this issue aside, and the outages, pushing to a private repo takes _minutes_ now, and file lists in the web interface often don't load without a page refresh.

At the price and size of Linode instances, it's cheaper and I feel better knowing I'm in control when I run Redmine+Gitosis. When I had my github account and something went wrong, I couldn't just ssh in and fix it. All I could do is wait. Now, for some people, I can see how waiting is an easier solution. I personally just don't like it. (of course, this is reffering to private repos. public repos are still king on gi…

If you have that much time on your hands, just use github as your main repository source and Redmine+Gitosis as a secondary? Everybody with a git clone has a full copy of everything.

Re: GitHub major issues - repos have "lost" commits and site is erroring

#16

Post by SpiralLab »

windsurfer wrote: post #7
rabidsnail wrote: post #4

Is it just me or has guthub's performance and reliability been getting progressively worse over the past month or two? Even putting this issue aside, and the outages, pushing to a private repo takes _minutes_ now, and file lists in the web interface often don't load without a page refresh.

At the price and size of Linode instances, it's cheaper and I feel better knowing I'm in control when I run Redmine+Gitosis. When I had my github account and something went wrong, I couldn't just ssh in and fix it. All I could do is wait. Now, for some people, I can see how waiting is an easier solution. I personally just don't like it. (of course, this is reffering to private repos. public repos are still king on gi…

A major selling point of Git is the distributed part. You are allowed (even encouraged) to have more than one "source of truth". For ~7$/mo (including admin. and cheaper than Linode), GitHub is just another place to have a hosted version of your repo, with a nice UI and social features.

Shit happens, servers go down, that's why you also have a remote repo hosted on Linode, and X, and Y too.

Re: GitHub major issues - repos have "lost" commits and site is erroring

#17

Post by guywithabike »

rabidsnail wrote: post #4

Is it just me or has guthub's performance and reliability been getting progressively worse over the past month or two? Even putting this issue aside, and the outages, pushing to a private repo takes _minutes_ now, and file lists in the web interface often don't load without a page refresh.

It's just you.

My team uses dozens of private repos hundreds of times a day and everything's been smooth for the past few months, aside from the disruptions noted on their status blog.

Re: GitHub major issues - repos have "lost" commits and site is erroring

#18

Post by andrewljohnson »

guywithabike wrote: post #17
rabidsnail wrote: post #4

Is it just me or has guthub's performance and reliability been getting progressively worse over the past month or two? Even putting this issue aside, and the outages, pushing to a private repo takes _minutes_ now, and file lists in the web interface often don't load without a page refresh.

It's just you. My team uses dozens of private repos hundreds of times a day and everything's been smooth for the past few months, aside from the disruptions noted on their status blog.

It's not _just_ him. Right now, it's me too.

Re: GitHub major issues - repos have "lost" commits and site is erroring

#20

Post by saurik »

SpiralLab wrote: post #16
windsurfer wrote: post #7

Earlier quoted context omitted.

At the price and size of Linode instances, it's cheaper and I feel better knowing I'm in control when I run Redmine+Gitosis. When I had my github account and something went wrong, I couldn't just ssh in and fix it. All I could do is wait. Now, for some people, I can see how waiting is an easier solution. I personally just don't like it. (of course, this is reffering to private repos. public repos are still king on gi…

A major selling point of Git is the distributed part. You are allowed (even encouraged) to have more than one "source of truth". For ~7$/mo (including admin. and cheaper than Linode), GitHub is just another place to have a hosted version of your repo, with a nice UI and social features. Shit happens, servers go down, that's why you also have a remote repo hosted on Linode, and X, and Y too.

This is an interesting theory, but it isn't how git's client actually works. If the repository exported a list of "mirrors" to the client that it then stored and was willing to use, that would be awesome, but otherwise you have a million people out there who are now just getting error messages when they do "git pull" and the only fix is for them to go back to your web page and try to get information on what is happening and where else they can switch their origin. Meanwhile, if you do your own hosting you can just update your DNS to point to another box and no one is the wiser.

They key problem, frankly, is that GitHub conflates two entirely unrelated things: a nice UI and social features, and a hosted version of your repo. I love the idea of outsourcing a nice UI and having cool social features, and /maybe/ to make those features work they need to have a mirror of my repository (I'm not convinced), but when people go to pull it the URL listed should be the actual upstream "I own the DNS on this and feel I can make this stable in the long term", not the GitHub mirror.

Post reply on HN