First of all thanks to everybody for an amazing tool! I’m a big fan of
it, so I’m trying to get rid of CVS in my company and migrate to Git.
We are working in, I would say, standard corporate environment, so all
development is in internal network. We have multiple offices in
different countries. Currently as I said we are using CVS (don’t
ask!;))
My problem is that I need the simplest, easiest and fastest solution
from setup and maintenance point of view in a situation when we have a
huge CVS repo with hundreds of modules (projects) in it. My current
understanding is that we are going to pull out project by project from
CVS and create corresponding git repos.
So, this brings us to hundreds of git repos and over 200 hundred
committers. In this circumstances we don’t want to manage each repo
separately as well as we don’t want to manage each person write access
rights to each repo.
As I understand the best solution here is git protocol (one port only
on dedicated server and no security as we are in trusted network) with
read and write access configured for all repos on a dedicated server.
What do you think I should do? How to enable push over git protocol?
I would appreciate any recommendation about such set up and any links
to corresponding docs.
Thank you,
Eugene
On Wed, Sep 30, 2009 at 04:13:23PM -0700, Eugene Sajine wrote:
As I understand the best solution here is git protocol (one port only
on dedicated server and no security as we are in trusted network) with
read and write access configured for all repos on a dedicated server.
What do you think I should do? How to enable push over git protocol?
You can pass --enable=receive-pack but it probably isn't what you
want. Anybody can write anything, anywhere with that, and more
importantly, anybody can delete anything.
When we started with git, we had a single machine that housed the
repos. It ran a read-only git server, and people used ssh to
push to it. It doesn't require accounts on the machine, but you
can use git-shell to restrict access. This is probably a good
way to start out.
Eventually, it's possible to realize that there doesn't need to
be _the_ central server. There can be several, and different
people in charge of different parts. Here at least, people never
really adapted to this model.
We're now primarily using Gerrit, but that's a larger step from
process change from CVS.
David Brown
Eugene Sajine [off-list ref] writes:
My problem is that I need the simplest, easiest and fastest solution
from setup and maintenance point of view in a situation when we have a
huge CVS repo with hundreds of modules (projects) in it. My current
understanding is that we are going to pull out project by project from
CVS and create corresponding git repos.
So, this brings us to hundreds of git repos and over 200 hundred
committers. In this circumstances we don’t want to manage each repo
separately as well as we don’t want to manage each person write access
rights to each repo.
As I understand the best solution here is git protocol (one port only
on dedicated server and no security as we are in trusted network) with
read and write access configured for all repos on a dedicated server.
What do you think I should do? How to enable push over git protocol?
No, I don't think it is a good solution, as git protocol is by design
anonymous and unauthenticated.
To enable push via git protocol, you have to enable 'receive-pack'
service for git-daemon (the --enable=<service> option).
I would appreciate any recommendation about such set up and any links
to corresponding docs.
You would probably want to use some tool to manage git repositories,
like
* Gitosis (in Python, requires setuptools),
* Gitolite (in Perl),
* SCuMD (in Java),
or even
* ssh_acl
I think Gitosis is most commonly used tool, see links in
http://git.or.cz/gitwiki/InterfacesFrontendsAndTools and
http://git.or.cz/gitwiki/BlogPosts pages on git wiki.
There are also full-fledged git hosting solutions, usually with web
interface to git repositories administration:
* GitHub:FI (proprietary, non-free)
* Gitorious (Ruby on Rails)
* InDefero (PHP, clone of Google Code)
* Girocco (Perl + bash, used by http://repo.or.cz)
There are also tools such as repo and Gerrit from Android project
(Gerrit is a review board).
Also, depending on workflow used, you might not need for anyone beside
project maintainer to have push access to public repository;
maintainer would process pull requests from co-developers, from their
per-developer forks.
--
Jakub Narebski
Poland
ShadeHawk on #git