From: Jeff King <peff@peff.net>
To: Paul Tarjan <ptarjan@gmail.com>
Cc: Jakub Narebski <jnareb@gmail.com>,
git@vger.kernel.org, yury239@gmail.com
Subject: Re: Git Confusion
Date: Fri, 29 May 2009 16:38:54 -0400 [thread overview]
Message-ID: <20090529203854.GA14326@coredump.intra.peff.net> (raw)
In-Reply-To: <815c8c330905291324w4e861602n8278df72fdbc28db@mail.gmail.com>
On Fri, May 29, 2009 at 01:24:59PM -0700, Paul Tarjan wrote:
> The reason I need http is slightly convoluted. The remote machine is
> shared hosting with 1 ssh login that I don't want to give to my
> partner AND I don't have root on that box. And as you correctly
> guessed, that box doesn't have the git demon. The local machine where
> he is doing his development. The only solution I saw without giving
> him my username + pass to SSH was to do http cloning. Any better
> solutions?
You can let him login via ssh key and restrict the actions of that key
just to running git-upload-pack (which is what "git clone" and "git
fetch" will invoke to clone or fetch commits). Something like:
command="git-upload-pack /path/to/repo" ssh-rsa ...
in your .ssh/authorized_keys file. Not that he still won't be able to
actually push (which is maybe what you want).
For a more featureful solution (with permissions for pushing and pulling
multiple repos), I think gitosis will do what you want (but I have never
used it personally).
-Peff
next prev parent reply other threads:[~2009-05-29 20:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-29 7:43 Git Confusion Paul Tarjan
2009-05-29 12:58 ` Jeff King
2009-05-29 13:44 ` Jakub Narebski
2009-05-29 13:52 ` Jeff King
2009-05-29 20:24 ` Paul Tarjan
2009-05-29 20:28 ` Avery Pennarun
2009-05-29 20:38 ` Jeff King [this message]
2009-05-30 0:41 ` Sitaram Chamarty
2009-05-29 20:45 ` Jakub Narebski
2009-05-30 1:32 ` 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=20090529203854.GA14326@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=ptarjan@gmail.com \
--cc=yury239@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).