From: "J. Bakshi" <joydeep@infoservices.in>
To: unlisted-recipients:; (no To-header on input)
Cc: Sitaram Chamarty <sitaramc@gmail.com>, git@vger.kernel.org
Subject: Re: git pre-push hook to restrict master branch push !!!
Date: Wed, 20 Jun 2012 18:09:47 +0530 [thread overview]
Message-ID: <20120620180947.755a96ba@shiva.selfip.org> (raw)
In-Reply-To: <20120611174757.2f0bdd83@shiva.selfip.org>
On Mon, 11 Jun 2012 17:47:57 +0530
"J. Bakshi" <joydeep.bakshi@infoservices.in> wrote:
> On Mon, 11 Jun 2012 17:40:37 +0530
> Sitaram Chamarty <sitaramc@gmail.com> wrote:
>
> > On Mon, Jun 11, 2012 at 4:48 PM, J. Bakshi
> > <joydeep.bakshi@infoservices.in> wrote:
> > > Hello list,
> > >
> > > I have a central server where git repos are located and based on http base push/pull.
> > > authentication is done by a text based password file, generated by htpasswd.
> > >
> > > I am searching for a server side hook (pre-push) which can prevent all push to master,
> > > except few users found at that password file generated by htpasswd. Is there any such hook
> > > available ? Some suggest to use gitolite, but it also based on the hooks to do the same.
> >
> > If you don't want to use gitolite, you can roll your own update hook.
> > It can be as simple as
> >
> > - check $REMOTE_USER to see if the name is in the "allowed" list
> > (your choice how you want to maintain that list). If allowed, 'exit
> > 0".
> > - otherwise check $1 (argument 1) to see if it is
> > "refs/heads/master". If it is, "exit 1".
> >
> > How difficult is that?
>
> Thanks for the clue. I'm not familiar with the hook programming.
> I'll check further with the clues you have given.
>
> -- with regards.
> --
The refs/heads/master checking is fine. Can I placed this checking
in my httpd.conf file to check user against a htpasswd file ?
Thanks
prev parent reply other threads:[~2012-06-20 12:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-11 11:18 git pre-push hook to restrict master branch push !!! J. Bakshi
2012-06-11 12:10 ` Sitaram Chamarty
2012-06-11 12:17 ` J. Bakshi
2012-06-20 12:39 ` J. Bakshi [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=20120620180947.755a96ba@shiva.selfip.org \
--to=joydeep@infoservices.in \
--cc=git@vger.kernel.org \
--cc=sitaramc@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).