From: John Haltiwanger <john.haltiwanger@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: RCS/git server (was: Transliterator module, 2nd revision)
Date: Thu, 11 Mar 2010 11:52:02 +0000 [thread overview]
Message-ID: <4c1f1f861003110352t38c52826j244870e2306f1505@mail.gmail.com> (raw)
In-Reply-To: <EE7D7DFB-7872-4CC6-BDD5-FE846F9A76CA@fiee.net>
[-- Attachment #1.1: Type: text/plain, Size: 3329 bytes --]
Another option is Gitosis:
http://swik.net/gitosis
from
http://scie.nti.st/2007/11/14/hosting-git-repositories-the-easy-and-secure-way:
"
I have been asked more and more these days, "How do I host a Git
repository?" Usually it is assumed that some access control beyond simply
read-only is involved (some users have commit rights). With access control
comes issues of security, and that's a whole other bag of cats. This post is
about presenting an answer to this question, without the fuss.
The rest of this article will be a tutorial showing you how to host and
manage Git repositories with access control, easily and safely. I use an up
and coming tool called *gitosis
<http://eagain.net/gitweb/?p=gitosis.git>*that my friend
Tv <http://eagain.net/> wrote to help make hosting git repos easier and
safer. It manages multiple repositories under one user account, using SSH
keys to identify users. *However, users do *not* need shell accounts on the
server, instead they will talk to one shared account that does not allow
arbitrary commands.* Git itself is used to setup gitosis and manage the Git
repos, which pleases the recursion-seeking orthogonal CS-side of my brain.
"
On Thu, Mar 11, 2010 at 7:44 AM, Henning Hraban Ramm <hraban@fiee.net>wrote:
> Am 2010-03-10 um 23:09 schrieb Mojca Miklavec:
>
> On Wed, Mar 10, 2010 at 17:01, Wolfgang Schuster wrote:
>>
>>> Am 10.03.10 10:47, schrieb Philipp Gesang:
>>>
>>>>
>>>> I have opened a bitbucket account in order to not to clutter the mailing
>>>> list with archives. The tip revision can be found here:
>>>> http://bitbucket.org/phg/transliterator/get/2fc2b5fbbd46.gz
>>>> and the precompiled manual over here:
>>>> http://bitbucket.org/phg/transliterator/downloads/transliterator.pdf
>>>>
>>>
>>> Can you also add the module to the module section [1] on the wiki,
>>>
>>
>> We urgently need to have some "git server" or something similar on the
>> garden for modules. Maybe SVN would also do for a while. The current
>> approach is very clumsy to use.
>>
>
> see
> http://www.kernel.org/pub/software/scm/git/docs/user-manual.html#public-repositories
>
> If the web server running supports WebDAV, we could use that:
>
> http://www.kernel.org/pub/software/scm/git/docs/howto/setup-git-server-over-http.txt
>
> Otherwise you'd need to run git daemon (usually on port 9418):
> http://www.kernel.org/pub/software/scm/git/docs/git-daemon.html
>
> For my non-public projects I just access the repos on my webserver via ssh,
> but that wouldn't be enough for ConTeXt modules - or perhaps it would, if
> everyone gets his/her own user account and you/Patrick can link that into
> the module store.
>
> Greetlings from Lake Constance!
> Hraban
> ---
> http://www.fiee.net/texnique/
> http://wiki.contextgarden.net
> https://www.cacert.org (I'm an assurer)
>
>
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to
> the Wiki!
>
> maillist : ntg-context@ntg.nl /
> http://www.ntg.nl/mailman/listinfo/ntg-context
> webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
> archive : http://foundry.supelec.fr/projects/contextrev/
> wiki : http://contextgarden.net
>
> ___________________________________________________________________________________
>
[-- Attachment #1.2: Type: text/html, Size: 5439 bytes --]
[-- Attachment #2: Type: text/plain, Size: 486 bytes --]
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2010-03-11 11:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-10 9:47 Transliterator module, 2nd revision Philipp Gesang
2010-03-10 16:01 ` Wolfgang Schuster
2010-03-10 22:09 ` Mojca Miklavec
2010-03-11 7:44 ` RCS/git server (was: Transliterator module, 2nd revision) Henning Hraban Ramm
2010-03-11 11:52 ` John Haltiwanger [this message]
2010-03-11 8:06 ` Transliterator module, 2nd revision Patrick Gundlach
2010-03-11 9:28 ` VCS for modules (was: Re: Transliterator module, 2nd revision) Peter Münster
2010-03-11 9:31 ` luigi scarso
2010-03-11 11:12 ` Mojca Miklavec
2010-03-11 12:03 ` VCS for modules Hans Hagen
2010-03-11 11:25 ` Transliterator module, 2nd revision Mojca Miklavec
2010-03-11 9:32 ` Philipp Gesang
2010-03-11 9:58 ` Jelle Huisman
2010-03-11 10:33 ` Hans Hagen
2010-03-12 9:42 ` Modules section login (Was: Transliterator module, 2nd revision) Philipp Gesang
2010-03-12 9:57 ` Patrick Gundlach
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=4c1f1f861003110352t38c52826j244870e2306f1505@mail.gmail.com \
--to=john.haltiwanger@gmail.com \
--cc=ntg-context@ntg.nl \
/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).