From: "Jason Pyeron" <jpyeron@pdinc.us>
To: "'git'" <git@vger.kernel.org>
Subject: RE: Trying to understand the web dav details
Date: Sun, 6 Jan 2013 01:20:56 -0500 [thread overview]
Message-ID: <A18DA90EFF3743E5B580CBC68F1C9F7C@black> (raw)
In-Reply-To: <20130106053807.GA8551@sigill.intra.peff.net>
Ignore everything below, it was a case sensitive typo. It always worked it.
> -----Original Message-----
> From: Jeff King
> Sent: Sunday, January 06, 2013 0:38
>
> On Sun, Jan 06, 2013 at 04:49:57AM +0000, Pyeron, Jason J CTR
> (US) wrote:
>
> > > > How does the ?service=xxxx get translated in to the action
> > > > performed on the web server?
> > >
> > > If you are using the git-http-backend CGI, it will interpret the
> > > service
> >
> > No, using plain jane http and webdav. This server is not
> "allowed" to
> > use cgi processes.
>
> Then the service parameter should be ignored by your
> webserver, and it should just serve the info/refs file from
> the repository on the filesystem. And you are stuck using
> WebDAV for push.
>
> > > GET /git/project-x/info/refs HTTP/1.1
> > [...]
> > * The requested URL returned error: 404 Not Found
>
> Does the info/refs file exist in the project-x repository?
Yes.
>
> > fatal: https://server/git/project-x/info/refs not found:
> did you run git update-server-info on the server?
>
> Did you?
>
Many times.
> If you can't run any git programs on the server at all (and
> it sounds like that may be the case), you'll need to run it
> locally before putting the repository data on the server.
>
> Once you have WebDAV set up for pushing, it will update the
> info/refs file for each push. But if you are initially
> seeding the server with rsync or a tarfile, you'll want to
Seeding it seems to work, it is the bare init that seems to be failing. Might be
on to something there.
> make sure it has an up-to-date info/refs file.
Here is the create script:
#!/bin/bash
if [ $# != 1 ]; then
exit 1;
fi
if [ -e "$1" ]; then
exit 2;
fi
mkdir "$1"
cd "$1"
git init --bare
cp hooks/post-update.sample hooks/post-update
chmod +x hooks/post-update
git update-server-info
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
- -
- Jason Pyeron PD Inc. http://www.pdinc.us -
- Principal Consultant 10 West 24th Street #100 -
- +1 (443) 269-1555 x333 Baltimore, Maryland 21218 -
- -
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
This message is copyright PD Inc, subject to license 20080407P00.
prev parent reply other threads:[~2013-01-06 6:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-06 1:32 Trying to understand the web dav details Jason Pyeron
2013-01-06 4:19 ` Jeff King
2013-01-06 4:49 ` Pyeron, Jason J CTR (US)
2013-01-06 5:38 ` Jeff King
2013-01-06 6:20 ` Jason Pyeron [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=A18DA90EFF3743E5B580CBC68F1C9F7C@black \
--to=jpyeron@pdinc.us \
--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