git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc Singer <elf@buici.com>
To: git@vger.kernel.org
Subject: Re: gitweb testing with non-apache web server
Date: Thu, 3 Aug 2006 13:27:03 -0700	[thread overview]
Message-ID: <20060803202703.GA13147@buici.com> (raw)
In-Reply-To: <20060803192152.GT7533@daga.cl>

On Thu, Aug 03, 2006 at 03:21:52PM -0400, Blu Corater wrote:
> Here is the interesting part of my cherokee.conf
> 
> ------------------------------------------
> UserDir public_html {
>     Directory / {
>        Handler common
>     }
> 
>     Directory /scm/ {
>         Handler cgi {
>                 ScriptAlias /home/blu/bin/gitweb.cgi
>         }
>     }
> }
> -----------------------------------------
> 
> So, I have the gitweb.cgi executable in a bin directory on my home and I
> am telling Cherokee that when it sees the url http://server/~blu/scm/, it
> should execute /home/blu/bin/gitweb.cgi
> 
> If I request http://server/~blu/scm, Cherokee returns Cherokee's default
> index page. Only if I request http://server/~blu/scm/, Cherokee returns
> the expected output from gitweb.
> 
> Now, if I add 
> 
>     Directory /test/ {
> 	Handler cgi
>     }
> 
> And copy gitweb.cgi to ~/public_html/test/, it seems there is no problem.
> 
> I can request http://server/~blu/test/gitweb.cgi or
> http://server/~blu/test/gitweb.cgi/ and get the expected gitweb output.
> 
> It looks more like a Cherokee problem to me, but I don't have time to
> investigate further right now.

Hmm.  I was hopeful when I saw that your configuration was different
from mine.  However, it seems to be something else.  BTW, I'm running
cherokee on ARM.

========================================
Directory / {
    Handler common
}

Directory /g/ {
    Handler cgi {
        Scriptalias /usr/lib/cgi-bin/git.cgi
    }
}
Directory /git/ {
    Handler cgi {
        Scriptalias /usr/lib/cgi-bin/gitweb.cgi
    }
}
========================================

gitweb.cgi is an old version.  git.cgi is the latest release.

I can see the project overview page, but all of the links bring me
back to the same top-level page, no summary, not logs.  I've verified
that the web server's user can read the git repo. 

I don't doubt that this is a cherokee issue.

Cheers.

  reply	other threads:[~2006-08-03 20:27 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 [this message]
2006-08-03 23:55         ` Francis Daly
2006-08-04  6:11           ` Marc Singer
2006-08-04 19:48             ` Francis Daly
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=20060803202703.GA13147@buici.com \
    --to=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).