Re: git push over http - curl PUT error?

From: aaron smith <beingthexemplarylists@gmail.com>
Date: Dec 31, 2008, 13:29 UTC
Message-ID: <d7ac1a680812310529p6b7e8d88r69755887304d3436@mail.gmail.com>
In-Reply-To: <d7ac1a680812310210r25795e66x35601059103892d7@mail.gmail.com>

ok, duh, i had to use git http-push. What is the difference? Thanks.

On Wed, Dec 31, 2008 at 2:10 AM, aaron smith <beingthexemplarylists@gmail.com> wrote:

Show 38 quoted lines

> hey all,
>
> I have one last issue to figure out with git over HTTP. This one is
> seriously stumping me.
>
> I have a bare git repository here: http://codeendeavor.com/guttershark.git/
>
> And I have a local git repo with some files in it, ready to push to
> this public one.
>
> Here's what I do to push to it:
>
> $git push origin master
>
> I then get this output:
> ""
> Fetching remote heads...
>  refs/
>  refs/heads/
>  refs/tags/
> updating 'refs/heads/master'
>  from a08e614723ff57047522511a2130d53010ebe0ca
>  to   2db4bca0d137f4099973387472cf1666d0290e03
>    sending 3 objects
>    done
> Updating remote server info
> PUT error: curl result=22, HTTP code=403
> """
>
> I'm not sure how to get around this.
>
> The git repo permissions are 777, with owner/group apache:apache. I
> have DAV on, and the DavLockDB directive. which seems to all be ok.
> And I don't have any http authentication on it.. or access control
> list for that matter.
>
> Any ideas? Thanks All!
>