From: Jeff King <peff@peff.net>
To: Shlomit Afgin <shlomit.afgin@weizmann.ac.il>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Error in creating git over http
Date: Wed, 9 Oct 2013 21:06:17 -0400 [thread overview]
Message-ID: <20131010010616.GA14429@sigill.intra.peff.net> (raw)
In-Reply-To: <51123DD1BF2E03418A1296748DA730927454504A@ibwmbx03>
On Tue, Oct 08, 2013 at 03:05:22PM +0000, Shlomit Afgin wrote:
> I do the following on the git server:
> cd /var/www/html/
> git clone --bare /path/to/dir/ gitproject.git
> cd gitproject.git/
> mv hooks/post-update.sample hooks/post-update
> chmod a+x hooks/post-update
OK, so on the next push, the info/refs file should be updated. Note that
this file is only necessary if you want to run the "dumb" http protocol
(i.e., the less efficient one that does not require git on the server).
You didn't say whether you are trying to set up a "dumb" or "smart"
git-http server. These days you almost certainly want to set up a
"smart" one, and you do not need to care about info/refs or running
update-server-info.
> on the local machine run:
> git clone http://server.name/gitproject.git
>
> I got the error:
> "Initialized empty Git repository in /local/path/gitproject/.git/
> fatal: http://server.name/gitproject.git/info/refs not found: did you run
> git update-server-info on the server?"
>
> I saw that the file does not exist, it seem that the file post-update is
> not execute.
Yes, if you didn't push yet, then it won't have been created.
> I run it on the git server:
> git update-server-info
>
> Now the info/ref is created.
OK, good.
> On local machine I run again :
> git clone http://server.name/gitproject.git
>
> Now I get the error:
> Initialized empty Git repository in /local/path/gitproject/.git/
> error: The requested URL returned error: 403 (curl_result = 22, http_code
> = 403, sha1 = 9d83b83df9fbc75ecd754264f95793fca93ccf93)
> error: Unable to find 9d83b83df9fbc75ecd754264f95793fca93ccf93 under
> http://server.name/gitproject.git
> Cannot obtain needed object 9d83b83df9fbc75ecd754264f95793fca93ccf93
403 is an HTTP "Forbidden". Have you configured your web server to allow
access to the project? Have you marked the repository as
git-daemon-export-ok, as described in "git help http-backend" (or set
GIT_HTTP_EXPORT_ALL in the environment)? Is there anything interesting
in the webserver's error logs?
If it is still not working after checking those things, can you show us
how you have configured your webserver (presumably apache?).
-Peff
next prev parent reply other threads:[~2013-10-10 1:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <51123DD1BF2E03418A1296748DA730927454460F@ibwmbx03>
2013-10-08 15:05 ` Error in creating git over http Shlomit Afgin
2013-10-10 1:06 ` Jeff King [this message]
2013-10-10 5:25 ` Shlomit Afgin
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=20131010010616.GA14429@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=shlomit.afgin@weizmann.ac.il \
/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).