From: Mike Hommey <mh@glandium.org>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Nikolai Prokoschenko <nikolai@prokoschenko.de>, git@vger.kernel.org
Subject: Re: Push over WebDAV and hooks
Date: Thu, 21 Aug 2008 23:15:10 +0200 [thread overview]
Message-ID: <20080821211510.GA18403@glandium.org> (raw)
In-Reply-To: <20080821201126.GY3483@spearce.org>
On Thu, Aug 21, 2008 at 01:11:26PM -0700, Shawn O. Pearce wrote:
> Nikolai Prokoschenko <nikolai@prokoschenko.de> wrote:
> > I have a (bare) repository on my server. Since I need to access it from
> > firewalled networks, I can't go with git protocol or SSH; I thought
> > WebDAV is the way to go. However I've noticed that my hooks are not
> > executed and could not really think of a way the could ever work, since
> > WebDAV is essentially a virtual hard drive without any execution
> > capability. So am I right, hooks aren't supposed to work with WebDAV and
> > so I'd have to find a way to use SSH or git:// to push changes?
>
> Correct. Hooks can only be executed if you use SSH or git:// to push
> the changes, as there is no remote execution available via WebDAV.
>
> That said if someone was really interested in this they could try
> to make hook CGIs and teach git-http-push how to execute them by
> sending a GET to the proper URL. But then you are relying on the
> client to honor the hooks, and only newer clients (post that change)
> would support it.
One can surely set special PUT action scripts for some special files,
such as refs. But one needs to know how to write such action scripts
and to have enough apache/webserver priviledge to activate them.
Mike
prev parent reply other threads:[~2008-08-21 21:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-21 19:48 Push over WebDAV and hooks Nikolai Prokoschenko
2008-08-21 20:11 ` Shawn O. Pearce
2008-08-21 20:13 ` Nikolai Prokoschenko
2008-08-21 21:15 ` Mike Hommey [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=20080821211510.GA18403@glandium.org \
--to=mh@glandium.org \
--cc=git@vger.kernel.org \
--cc=nikolai@prokoschenko.de \
--cc=spearce@spearce.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).