git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Francis Daly <francis@daoine.org>
To: Marc Singer <elf@buici.com>
Cc: git@vger.kernel.org
Subject: Re: gitweb testing with non-apache web server
Date: Fri, 4 Aug 2006 20:48:40 +0100	[thread overview]
Message-ID: <20060804194840.GM17966@craic.sysops.org> (raw)
In-Reply-To: <20060804061122.GA15755@buici.com>

On Thu, Aug 03, 2006 at 11:11:22PM -0700, Marc Singer wrote:
> On Fri, Aug 04, 2006 at 12:55:36AM +0100, Francis Daly wrote:

> > Or use a web server which isn't broken in this particular way.
> 
> :-) There doesn't seem to be much of the 'small' variety.  Though now
> I'll look into lighttpd as well.

I've had some success with thttpd, which is broken in a different way
which doesn't appear to affect gitweb.

$ cp gitweb.cgi g
$ thttpd -p 8080 -d . -c '/g' 
$ $BROWSER http://localhost:8080/g

for example.  Adjust the config to fit your overall site need, of course.

-h localhost, or -l /dev/null, or -D, may also be useful.  There's a Fine
Manual out there.

Good luck,

	f
-- 
Francis Daly        francis@daoine.org

  reply	other threads:[~2006-08-04 19:48 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-03  7:54 gitweb testing with non-apache web server Marc Singer
2006-08-03  8:18 ` Jakub Narebski
2006-08-03 15:34   ` Marc Singer
2006-08-03 15:48     ` Jakub Narebski
2006-08-03 16:20       ` Marc Singer
2006-08-03 18:21       ` Junio C Hamano
2006-08-03 18:37         ` Jakub Narebski
2006-08-03 19:41           ` Junio C Hamano
2006-08-03 20:14             ` Martin Waitz
2006-08-03 11:42 ` Sam Vilain
2006-08-03 15:56 ` Blu Corater
2006-08-03 16:22   ` Marc Singer
2006-08-03 19:21     ` Blu Corater
2006-08-03 20:27       ` Marc Singer
2006-08-03 23:55         ` Francis Daly
2006-08-04  6:11           ` Marc Singer
2006-08-04 19:48             ` Francis Daly [this message]
2006-08-04  7:30           ` Marc Singer

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=20060804194840.GM17966@craic.sysops.org \
    --to=francis@daoine.org \
    --cc=elf@buici.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.
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).