git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Bryan Turner <bturner@atlassian.com>
To: SHeinz@aaanortheast.com
Cc: Git Users <git@vger.kernel.org>
Subject: Re: git question from a newbie
Date: Tue, 5 Jun 2018 15:29:10 -0700	[thread overview]
Message-ID: <CAGyf7-GN=wx4cc7WxbmMweC0VSnp_9aZ8fTUGE0W6vLK63qpVw@mail.gmail.com> (raw)
In-Reply-To: <BN7PR15MB23394E6E4AB05C17287E8F55BB660@BN7PR15MB2339.namprd15.prod.outlook.com>

On Tue, Jun 5, 2018 at 2:33 PM Heinz, Steve <SHeinz@aaanortheast.com> 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

  parent reply	other threads:[~2018-06-05 22:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-05 21:24 git question from a newbie Heinz, Steve
2018-06-05 22:19 ` Randall S. Becker
2018-06-07 12:40   ` Heinz, Steve
2018-06-05 22:29 ` Bryan Turner [this message]
2018-06-07 12:46   ` Heinz, Steve

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAGyf7-GN=wx4cc7WxbmMweC0VSnp_9aZ8fTUGE0W6vLK63qpVw@mail.gmail.com' \
    --to=bturner@atlassian.com \
    --cc=SHeinz@aaanortheast.com \
    --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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).