git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Goran Mekić" <meka@ns-linux.org>
To: <git@vger.kernel.org>
Subject: Re: Git push from bare repo
Date: Fri, 28 May 2010 14:28:27 +0200	[thread overview]
Message-ID: <3529f1c81d1062a941056914c612d8c2@ns-linux.org> (raw)
In-Reply-To: <4BFF89A5.7020802@op5.se>


On Fri, 28 May 2010 11:15:17 +0200, Andreas Ericsson <ae@op5.se> wrote:
> On 05/28/2010 08:57 AM, Goran Mekić wrote:
>> 
>>      I have to push from first server to second (yeah, the names are
>>      great
>> :o) when ever someone pushes to first server. It should be done using
>> post-receive hook, for example. The problem is that I can not specify
ssh
>> key, and even if I could, anything but 600 perm for the key is
rejected.
>> What would be the best way to acomplish this? Thanx!
>> 
> 
> Why can't you specify ssh key, and why can't you set the key to have
perms
> 0600 and let it reside in a directory with perms 0700?
> 
> The post-receive hook is just a shell-script, basically.
    There's more then one developer and 600 is set to just one user.
Post-receive hook is executed as developer doing push. The accounts are in
LDAP, but I can't set all their UID number to same number because it's
used
for PAM. I was thinking about ACL. Is that even a solution? The dumb one
would be cron, but I wish I avoid pushing when there's no change.

-- 
FreeB(eer)S(ex)D(rugs) are the real daemons

  reply	other threads:[~2010-05-28 12:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-28  6:57 Git push from bare repo Goran Mekić
2010-05-28  9:15 ` Andreas Ericsson
2010-05-28 12:28   ` Goran Mekić [this message]
2010-05-28 12:59     ` BJ Hargrave
2010-05-29 11:01       ` Gelonida

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=3529f1c81d1062a941056914c612d8c2@ns-linux.org \
    --to=meka@ns-linux.org \
    --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).