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

21–30 of 91 posts

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

#22

Post by __david__ »

hsuma wrote: post #8

I'm still on the fence about that whole cloud thing, personally.

Well, here's the beauty of Github--if they lose all my repos I just don't care. Since I've got a copy of my repos locally, there's absolutely nothing they can lose... Worse case if they go completely down for a couple days I can still collaborate using ssh or "git send-email".

This is the only reason I decided to use Github after avoiding Sourceforge and their ilk for the past decade and a half.

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

#24

Post by jamesbritt »

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.

I have two repos living in "Repository temporarily unavailable" status for several days now. I understand that shit happens, but what's really frustration is inquiry about what can or will be done about it and getting no response.

Do I wait? Do I just move stuff to my own server? Go back to Gitorious?

It's not that I can't keep working, but the main reason I use Github is to make my OSS projects available. For other things I run my own server and my own git host. Having a project unavailable to people for days, when I'm trying to get bug fixes and such out, is not so good.

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

#25

Post by windsurfer »

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.

I'm a student, and I make a new git repo for each assignment or class. Github would become extremely expensive if I was to do this.

And my model for working on git projects is not distributed. We use a centralized model (which is totally viable and one of the many uses) instead of pull requests and branches. On small projects, I find this faster and easier for people to use.

Yes, I have backups, but when my centralized repo goes down, it's annoying to tell people to start pushing and pulling to a USB drive. Workflow is the issue, not losing work.

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

#26

Post by baddox »

jameskilton wrote: post #21
hsuma wrote: post #8

I'm still on the fence about that whole cloud thing, personally.

Not sure how this is relevant. Github isn't hosted on any cloud. http://www.anchor.com.au/blog/2009/09/github-designing-succe...

Well, every resource is locally on some physical machine somewhere. I think his point is that Github is often treated by its users as a "local" resource, in that it takes the place of what would otherwise be a local server running a Git front end or repository.

Now, Github probably wouldn't encourage total reliance on their service. Git is fundamentally distributed, so this doesn't have to be a problem. Still, the Github service is an integral part of many developers' workflow, and I do agree with the above commenter that I'm not sold on the idea of trusting remote servers with integral steps in my workflow.

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

#27

Post by bjg »

windsurfer wrote: post #25
SpiralLab wrote: post #16

Earlier quoted context omitted.

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.

I'm a student, and I make a new git repo for each assignment or class. Github would become extremely expensive if I was to do this. And my model for working on git projects is not distributed. We use a centralized model (which is totally viable and one of the many uses) instead of pull requests and branches. On small projects, I find this faster and easier for people to use. Yes, I have backups, but when my centraliz…

You mentioned Github would be prohibitively expensive if you were to use it for all of your school assignments?

Github actually has a program where if you tell them you are a student/professor you can get free private repo's.

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

#28

Post by jamesbritt »

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.

"GitHub is just another place to have a hosted version of your repo, with a nice UI and social features."

The main point of Github is the social aspect; git just makes that easier.

They were other public git hosts before, but they didn't get the traction of GitHub because they didn't offer the same magic as The Place to share code.

It's git hub for a reason.

Post reply on HN