Does git have the equivalent of "hg serve"?
That would be git-web. It's not built-in, but a set of Perl scripts that are invoked via CGI from Apache or similar. Setup is a snap as it can be installed with apt-get/yum/zypper.
How to set up your own private Git server on Linux
51–60 of 66 posts
Re: How to set up your own private Git server on Linux
#52Is there any point in putting obvious things that anyone can google when he need them on HN main page?
The value is not only in the post but in the subsequent discussion it generates.
In fact, I will often "cheat" and read the discussion first.
Re: How to set up your own private Git server on Linux
#53Why would one need a git server? I am somewhat unclear on this... any good reads on this topic? I am using git because I hate svn (so I use git-svn), so I am curious how a pure git setup would work...
easier collaboration with others that you need privacy on. A backup of your repos(though you should have backups on this too). a canonical version of your repository with read access for your team but commit access for only a select few.
I am sure there are more scenarios but this is just what I could think of in a min.
Re: How to set up your own private Git server on Linux
#54Earlier quoted context omitted.
The backups aren't as important as each git repo is a fully blown code. If your local repo is destroyed, you still have the server copy. If your server blows up, you still have the local copy. There are many other good reasons for a service like Github, like the excellent collaboration features, the really good repository and history browser or the good bugtracker. If you don't need those (small team, working alone)…
What legal issues/other issues from uploading your code to GitHub are you worried about? I can't imagine that GitHub would steal your code. They've never heard of you, they have no reason to believe your code is worth anything to them, and one "I have pretty damn good evidence that GitHub stole my code" could ruin their entire business. You mentioned legal issues. Are you afraid someone's going to ... subpoena your c…
Re: How to set up your own private Git server on Linux
#55Earlier quoted context omitted.
The backups aren't as important as each git repo is a fully blown code. If your local repo is destroyed, you still have the server copy. If your server blows up, you still have the local copy. There are many other good reasons for a service like Github, like the excellent collaboration features, the really good repository and history browser or the good bugtracker. If you don't need those (small team, working alone)…
What legal issues/other issues from uploading your code to GitHub are you worried about? I can't imagine that GitHub would steal your code. They've never heard of you, they have no reason to believe your code is worth anything to them, and one "I have pretty damn good evidence that GitHub stole my code" could ruin their entire business. You mentioned legal issues. Are you afraid someone's going to ... subpoena your c…
> Are you afraid someone's going to ... subpoena your code or something? Because if that happens, you'd have to turn it over anyway.
Not if you don't live in the US.
Re: How to set up your own private Git server on Linux
#56Hi Guys, This is a question I've been struggling with for a while now. Would you host your company's super important bread and butter code on GitHub instead of your own server? I get a funny feeling every time I think about this mostly because I've put tons of time (3 years) into our code base and I think of it as one of the most important aspects of our company. Then again, GitHub hosts their code on GitHub which ma…
I would, and I do. I don't use their wiki or issue tracker, though, so if they managed to lose the data, it'd take all of 30 seconds to (well, plus pushing some rather large files) to set it up again.
Our codebase is GPLed, so there are no concerns about privacy.
Re: How to set up your own private Git server on Linux
#57Is there any point in putting obvious things that anyone can google when he need them on HN main page?
The value is not only in the post but in the subsequent discussion it generates. In fact, I will often "cheat" and read the discussion first.
You must be a recovering slashdotter, like me.
Re: How to set up your own private Git server on Linux
#58Does git have the equivalent of "hg serve"?
That would be git-web. It's not built-in, but a set of Perl scripts that are invoked via CGI from Apache or similar. Setup is a snap as it can be installed with apt-get/yum/zypper.
Honest question: What's the easiest way for two developers using git to push and pull from each other, if they're running Windows and on an isolated LAN?
Re: How to set up your own private Git server on Linux
#59Earlier quoted context omitted.
Or... ssh bob@example.com 'cat >> .ssh/authorized-keys' < ~/.ssh/id_rsa.pub
This is not an idempotent operation, and I would not recommend this for anything besides a one-off event.
Interesting, I hadn't thought about it since, for my usage, setting up keys is pretty much always a one-off event (and pretty rare on top of that). What are the consequences of dropping your key into authorized_keys files multiple times? Tried it out on a Debian box, and didn't see any issues other than the obvious clutter.
Re: How to set up your own private Git server on Linux
#60Earlier quoted context omitted.
The backups aren't as important as each git repo is a fully blown code. If your local repo is destroyed, you still have the server copy. If your server blows up, you still have the local copy. There are many other good reasons for a service like Github, like the excellent collaboration features, the really good repository and history browser or the good bugtracker. If you don't need those (small team, working alone)…
What legal issues/other issues from uploading your code to GitHub are you worried about? I can't imagine that GitHub would steal your code. They've never heard of you, they have no reason to believe your code is worth anything to them, and one "I have pretty damn good evidence that GitHub stole my code" could ruin their entire business. You mentioned legal issues. Are you afraid someone's going to ... subpoena your c…
I don't live in the US. Our company isn't based in the US. While I'm somewhat familiar with US legislation by reading HN, I certainly don't feel comfortable to upload my code to US based servers of a US company as I plainly don't know their laws well enough to trust them with my companies intellectual property.
Of course, I could always trust them for now and instantly remove my stuff when there are signs of trouble, but I asked them (a year ago) whether deletions are instant and irreversible and they told me the usual thing: repositories are not instantly deleted so they could restore them in case of accidental deletions. In addition they stay around in backups for an indefinite time.
Legislation not known well enough and no control over the removal of my code from their machines - call me paranoid, but these are good reasons not to upload my code to them.