Re: git question from a newbie

From: Bryan Turner <bturner@atlassian.com>
Date: Jun 5, 2018, 22:29 UTC
Message-ID: <CAGyf7-GN=wx4cc7WxbmMweC0VSnp_9aZ8fTUGE0W6vLK63qpVw@mail.gmail.com>
In-Reply-To: <BN7PR15MB23394E6E4AB05C17287E8F55BB660@BN7PR15MB2339.namprd15.prod.outlook.com>

On Tue, Jun 5, 2018 at 2:33 PM Heinz, Steve <SHeinz@aaanortheast.com> wrote:

Show 12 quoted lines

>
> Hi.
>
> I am new to Git and have read quite a few articles on it.
> I am planning on setting up a remote repository on a windows 2012 R2 server and will access it via HTTPS.
> I am setting up a local repository on my desk top (others in my group will do the same).
> On "server1":  I install Git and create a repository "repos".
> On "server1":  I create a dummy webpage "default.htm" and place it in the repo folder.
> On "server1":  I create a web application in IIS pointing to Git
> On Server1":   change permissions so IIS_User  has access to the folders.
> On "server1":  inside the "repos" folder and right click and choose "bash here"
> On "server1":   $ git init  -bare    (it's really 2 hyphens)

This might create a _repository_, but it's not going to set up any Git hosting processing for it. You might be able to clone using the fallback to the "dumb" HTTP protocol (though I doubt it, with the steps you've shown) , but you won't be able to push.

You need handlers for git-http-backend which handle info/refs and other requests that are related to the Git HTTP wire protocol.[1]

Documentation for setting up Git's HTTP protocol via Apache are pretty easy to find[2], but IIS instructions are a bit more sparse. I don't know of any good ones off the top of my head. But that's your issue; your IIS setup isn't really a valid Git remote; it's just a Git repository with contents visible via HTTP.

[1] https://github.com/git/git/blob/master/Documentation/technical/http-protocol.txt [2] https://github.com/git/git/blob/master/Documentation/howto/setup-git-server-over-http.txt

Bryan