From: Sitaram Chamarty <sitaramc@gmail.com>
To: John McIntyre <joh98.mac@gmail.com>, Heiko Voigt <hvoigt@hvoigt.net>
Cc: git@vger.kernel.org
Subject: Re: Git Server Repository Security?
Date: Tue, 19 May 2015 06:05:53 +0530 [thread overview]
Message-ID: <555A8569.30607@gmail.com> (raw)
In-Reply-To: <CABQ4iYjwa-KmZAQV=p5efQYBZu3ymQRNwTC4TGXdpo4groArCA@mail.gmail.com>
On 05/18/2015 06:02 PM, John McIntyre wrote:
> All right, so I'm a bit confused. I followed the instructions to get
> gitolite, and put a public key, placing it on the server. I then
> run..
>
> ***
> gitolite setup -pk server-git01_rsa.pub
> Initialized empty Git repository in /home/git/repositories/gitolite-admin.git/
> Initialized empty Git repository in /home/git/repositories/testing.git/
> ***
>
> Our repositories are under /opt/git/n where n is the name of the repo.
Just use a symlink. Move ~/repositories to wherever you want and then
create a symlink at ~/repositories that points there.
Apologies for replying to some of your other message here, but
do not use /bin/nologin as the shell. It needs to be something that can
take "-c" parameter, so not even git-shell will work. Since all access
is controlled by the forced command in the authkeys file, this is not an
issue so just use bash or sh or whatever.
sitaram
next prev parent reply other threads:[~2015-05-19 0:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-18 10:07 Git Server Repository Security? John McIntyre
2015-05-18 10:26 ` Heiko Voigt
2015-05-18 10:58 ` John McIntyre
2015-05-18 11:57 ` Heiko Voigt
2015-05-18 12:32 ` John McIntyre
2015-05-18 12:39 ` Heiko Voigt
2015-05-18 15:07 ` John McIntyre
2015-05-18 19:15 ` Kevin Daudt
2015-05-19 0:35 ` Sitaram Chamarty [this message]
2015-05-18 12:18 ` Jason Cooper
2015-05-19 0:41 ` Sitaram Chamarty
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=555A8569.30607@gmail.com \
--to=sitaramc@gmail.com \
--cc=git@vger.kernel.org \
--cc=hvoigt@hvoigt.net \
--cc=joh98.mac@gmail.com \
/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).