git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eugene Sajine <euguess@gmail.com>
To: git@vger.kernel.org
Subject: Git push over git protocol for corporate environment
Date: Wed, 30 Sep 2009 19:13:23 -0400	[thread overview]
Message-ID: <76c5b8580909301613m283c4bfdne8de449ca0fd0987@mail.gmail.com> (raw)

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

             reply	other threads:[~2009-09-30 23:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-30 23:13 Eugene Sajine [this message]
2009-09-30 23:23 ` Git push over git protocol for corporate environment David Brown
2009-09-30 23:43 ` Jakub Narebski
     [not found]   ` <00163623ac5d75929b0474e66b96@google.com>
2009-10-02 14:41     ` Eugene Sajine
2009-10-02 14:47       ` Shawn O. Pearce
2009-10-02 15:58         ` Eugene Sajine
2009-10-02 18:54       ` Ismael Luceno
2009-10-04 15:25     ` Jakub Narebski
2009-10-04 16:26       ` Matthieu Moy
2009-09-30 23:54 ` Michael Poole
2009-10-01  0:06   ` Shawn O. Pearce
2009-10-01  6:29     ` Marius Storm-Olsen
2009-10-01 18:06       ` Shawn O. Pearce

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=76c5b8580909301613m283c4bfdne8de449ca0fd0987@mail.gmail.com \
    --to=euguess@gmail.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).