From: Jakub Narebski <jnareb@gmail.com>
To: Sitaram Chamarty <sitaramc@gmail.com>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
Junio C Hamano <gitster@pobox.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: should Documentation/howto/setup-git-server-over-http.txt be marked obsolete?
Date: Sat, 23 Oct 2010 00:24:50 -0700 (PDT) [thread overview]
Message-ID: <m3ocaljrs2.fsf@localhost.localdomain> (raw)
In-Reply-To: <AANLkTimTVviTBfY1Zeebyhufr36U+0w7VYf4f=25FMFi@mail.gmail.com>
Sitaram Chamarty <sitaramc@gmail.com> writes:
> On Fri, Oct 22, 2010 at 8:36 PM, Jonathan Nieder <jrnieder@gmail.com> wrote:
>> Sitaram Chamarty wrote:
>>
>>> I assumed that the new -- much more efficient (correct?) transport
>>> would make the older (dumber) transport obsolete, and I didn't realise
>>> it had any advantages over the new one.
>>
>> FWIW the old transport still has its place. If your web host (e.g.,
>> an ISP) allows only static content (no CGI), then there is no choice.
>>
>> Not so relevant for gitolite but still relevant in the world.
>
> Also I now realise the new transport requires Apache, so people with
> other web servers probably need it too.
Why do people think that "smart" HTTP transport requires Apache web
server? If I understand it correctly provided git-http-backend is a
simple CGI script, and requires CGI-capable web server and git
installed on server. Examples use Apache because probably that is
what author was familiar with. I don't see the reason why it
shouldn't work e.g. with nginx or IIS...
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2010-10-23 7:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-22 3:48 should Documentation/howto/setup-git-server-over-http.txt be marked obsolete? Sitaram Chamarty
2010-10-22 4:23 ` Junio C Hamano
2010-10-22 13:55 ` Sitaram Chamarty
2010-10-22 15:06 ` Jonathan Nieder
2010-10-23 6:27 ` Sitaram Chamarty
2010-10-23 7:24 ` Jakub Narebski [this message]
2010-10-22 18:36 ` Junio C Hamano
2010-10-23 6:29 ` Sitaram Chamarty
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=m3ocaljrs2.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
--cc=sitaramc@gmail.com \
/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).