From: Ismael Luceno <ismael.luceno@gmail.com>
To: Eugene Sajine <euguess@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Git push over git protocol for corporate environment
Date: Fri, 02 Oct 2009 15:54:45 -0300 [thread overview]
Message-ID: <4AC64C75.8090809@gmail.com> (raw)
In-Reply-To: <76c5b8580910020741p2024f6c0w70be53338924e7e8@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1077 bytes --]
Eugene Sajine escribió:
> I think that this is what is missing right now in order for git to get
> rocket start and spread inside companies: secure and easy to maintain
> mainline hosting.
>
It looks like your problem is using cygwin. It's more complicated on a
MS-Windows environment, and personally I think it's a _very bad idea_.
Git is really easy to use in fact, you just set up the repo with:
mkdir repo.git
cd repo.git
git init --bare --shared=all
--shared=all makes the repo readable to anyone, and ensures push rights
to users under the same group as the user setting up the repo. You can
change the group with chmod of course.
SSH access will be needed to push, unless the users can remotely mount
the repo via NFS or any other protocol.
Pulling is possible over http too, you just need to make
hooks/post-update executable. To export via git protocol you must create
an empty file named "git-daemon-export-ok".
Besides setting a web repo browser and git-server there's nothing else
specific to git.
--
Ismael Luceno
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2009-10-02 18:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-30 23:13 Git push over git protocol for corporate environment Eugene Sajine
2009-09-30 23:23 ` 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 [this message]
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=4AC64C75.8090809@gmail.com \
--to=ismael.luceno@gmail.com \
--cc=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).