Bryan
Thank you. I didn't realize that when you set up a remote repository, it is just a folder. I thought the fact that I had it setup as a website, was going to handle what I needed.
It wasn't until your email that I realized I had to use some type of client. I installed Bonobo as the remote repository and bam it worked!
You are right that the info on Windows is a bit sparse. I learned a lot and want to thank you again.
Steve Heinz
Steve Heinz | Lead Programmer Analyst, Information Technology
AAA Northeast | 1415 Kellum Place | Garden City, NY 11530
X8042 | T 516-535-2581 | F 516-873-2211
sheinz@xxxxxxxxxxxxxxxx | AAA.com
It Pays to Belong.
-----Original Message-----
From: Bryan Turner <bturner@xxxxxxxxxxxxx>
Sent: Tuesday, June 05, 2018 6:29 PM
To: Heinz, Steve <SHeinz@xxxxxxxxxxxxxxxx>
Cc: Git Users <git@xxxxxxxxxxxxxxx>
Subject: Re: git question from a newbie
On Tue, Jun 5, 2018 at 2:33 PM Heinz, Steve <SHeinz@xxxxxxxxxxxxxxxx> wrote:
>
> 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
The information contained in this email message is intended only for the private and confidential use of the recipient(s) named above, unless the sender expressly agrees otherwise. In no event shall AAA Northeast or any of its affiliates accept any responsibility for the loss, use or misuse of any information including confidential information, which is sent to AAA Northeast or its affiliates via email, or email attachment. AAA Northeast does not guarantee the accuracy of any email or email attachment. If the reader of this message is not the intended recipient and/or you have received this email in error, you must take no action based on the information in this email and you are hereby notified that any dissemination, misuse or copying or disclosure of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by email and delete the original message.
