git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Hommey <mh@glandium.org>
To: "Ask Bjørn Hansen" <ask@develooper.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Fix missing "HEAD" in the RewriteRule
Date: Sat, 7 Jun 2008 12:06:27 +0200	[thread overview]
Message-ID: <20080607100627.GA990@glandium.org> (raw)
In-Reply-To: <1212823166-25098-1-git-send-email-ask@develooper.com>

On Sat, Jun 07, 2008 at 12:19:26AM -0700, Ask Bjørn Hansen wrote:
> Also add a few more hints for how to setup and configure gitweb as described
> ---
>  gitweb/README |   18 ++++++++++++++----
>  1 files changed, 14 insertions(+), 4 deletions(-)
> 
> The important change is to add HEAD into the regexp, everything else is
> optional...
> 
> diff --git a/gitweb/README b/gitweb/README
> index 8f7ea36..b96834b 100644
> --- a/gitweb/README
> +++ b/gitweb/README
> @@ -255,12 +255,15 @@ Webserver configuration
>  If you want to have one URL for both gitweb and your http://
>  repositories, you can configure apache like this:
>  
> -<VirtualHost www:80>
> -    ServerName git.domain.org
> +<VirtualHost *:80>
> +    ServerName git.example.org
>      DocumentRoot /pub/git
> -    RewriteEngine on
> -    RewriteRule ^/(.*\.git/(?!/?(info|objects|refs)).*)?$ /cgi-bin/gitweb.cgi%{REQUEST_URI}  [L,PT]
>      SetEnv	GITWEB_CONFIG	/etc/gitweb.conf
> +    RewriteEngine on
> +    # make the front page an internal rewrite to the gitweb script 
> +    RewriteEngine ^/$  /cgi-bin/gitweb.cgi

You meant RewriteRule, right ?

Mike

  parent reply	other threads:[~2008-06-07 10:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-07  7:19 [PATCH] Fix missing "HEAD" in the RewriteRule Ask Bjørn Hansen
2008-06-07  9:16 ` Jakub Narebski
2008-06-07 10:06 ` Mike Hommey [this message]
2008-06-08  1:17 ` Junio C Hamano

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=20080607100627.GA990@glandium.org \
    --to=mh@glandium.org \
    --cc=ask@develooper.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).