From: Johan Herland <johan@herland.net>
To: git@vger.kernel.org
Cc: Tom Lanyon <tom@netspot.com.au>, pasky@suse.cz
Subject: Re: Internal, corporate, shared hosting solutions
Date: Fri, 26 Sep 2008 20:17:15 +0200 [thread overview]
Message-ID: <200809262017.15916.johan@herland.net> (raw)
In-Reply-To: <8B29890D-C03B-4ECE-9BEF-0A8E8EF7233E@netspot.com.au>
On Friday 26 September 2008, Tom Lanyon wrote:
> Hi list,
>
> I'm struggling. There's been a recent adoption of git here by our
> development staff, which is great. However, from an administrative
> point of view, I'm having trouble finding a solution to provide some
> kind of easy, shared, secure and accessible hosting solution to our
> developers.
>
> [...]
I'm pretty much in the exact same situation at $dayjob, and I'm
researching some alternatives as well. So far there seems to be a
couple of options:
1. Gitosis [1]. This is a fairly thin layer of Python scripts running as
a non-privileged "git" user on the server. All users authenticate by
registering their SSH key with Gitosis, and then access repos using
this one "git" user over SSH. Further access control (i.e. read/write
access to each repo) is done by Gitosis itself, and administered by
cloning a gitosis-admin repo, changing some configuration files and
pushing the result back to the server.
2. Gitorious [2]. Don't confuse this with the repo hosting service at
gitorious.org. You can clone the software that runs gitorious.org and
set it up on your own server. This is a much more heavy-weight
Ruby-on-Rails application that provides a nice web interface for
publishing and interacting with repositories. However, it is based on
the same underlying principle of registering your SSH-keys with
Gitorious, and running everything as a non-privileged "git" user.
3. repo.or.cz. I don't know much about how this work, and if it's easily
deployed on an in-house server. However, the repo.or.cz admin (Petr
Baudis, CCed) is active on this list, and can probably fill in the
details.
Feel free to keep me updated on your progress.
Have fun! :)
...Johan
[1]: Gitosis:
http://scie.nti.st/2007/11/14/hosting-git-repositories-the-easy-and-secure-way
Get it at http://eagain.net/gitweb/?p=gitosis.git;a=summary
[2]: Gitorious: http://gitorious.org/
Get it at http://gitorious.org/projects/gitorious
--
Johan Herland, <johan@herland.net>
www.herland.net
prev parent reply other threads:[~2008-09-26 18:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-26 15:13 Internal, corporate, shared hosting solutions Tom Lanyon
2008-09-26 15:39 ` Shawn O. Pearce
2008-09-26 18:17 ` Johan Herland [this message]
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=200809262017.15916.johan@herland.net \
--to=johan@herland.net \
--cc=git@vger.kernel.org \
--cc=pasky@suse.cz \
--cc=tom@netspot.com.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.