git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: gitweb testing with non-apache web server

From
BCBlu Corater <blu@daga.cl>
Date
Aug 3, 2006, 19:21 UTC
Message-ID
<20060803192152.GT7533@daga.cl>
In-Reply-To
<20060803162241.GB1287@buici.com>
On Thu, Aug 03, 2006 at 09:22:41AM -0700, Marc Singer wrote:
Show 48 quoted lines
> On Thu, Aug 03, 2006 at 11:56:03AM -0400, Blu Corater wrote:
> > On Thu, Aug 03, 2006 at 12:54:03AM -0700, Marc Singer wrote:
> > > I would like to use gitweb with the Cherokee web server because the
> > > host that I have on hand has very limited RAM, 32MiB.  Neither the
> > > version of gitweb available on Debian (v264) nor the latest in the git
> > > repo works.
> > > 
> > > I did some debugging on the latest repo version.  The lines
> > > 
> > >   our $project = ($cgi->param('p') || $ENV{'PATH_INFO'});
> > >   if (defined $project) {
> > >      ...
> > > 
> > > are being executed even though the url is
> > > 
> > >   http://server/git
> > > 
> > > I think that the problem is that Cherokee translates the request URL
> > > into
> > > 
> > >   http://server/git/
> > > 
> > > which means that the $ENV{'PATH_INFO'} is the string "/" insted of
> > > being undefined.
> > > 
> > > The error I'm seeing is that the request path is forbidden, but I
> > > suspect that this is some sort of misunderstanding between the web
> > > server and the script.
> > 
> > I am using Cherokee+GitWeb and the behaviour observed is that
> > http://server/git will return the default Cherokee index page, but
> > http://server/git/, with a slash at the end, works. 
> 
> Will you share your Cherokee configuration script?
> 
> The links look like this:
> 
>   http://scarlet/g?p=bsp.git;a=summary
> 
> even when I start with 
> 
>   http://scarlet/g
> 
> or
> 
>   http://scarlet/g/
> 
> So, I'm not sure I understand what you are saying.
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.

-- 
Blu.
Previous: Marc SingerNext: Marc Singer
Message 13 of 18 in “gitweb testing with non-apache web server”
  1. Marc SingerAug 3, 2006
  2. Jakub NarebskiAug 3, 2006
  3. Marc SingerAug 3, 2006
  4. Jakub NarebskiAug 3, 2006
  5. Marc SingerAug 3, 2006
  6. Junio C HamanoAug 3, 2006
  7. Jakub NarebskiAug 3, 2006
  8. Junio C HamanoAug 3, 2006
  9. Martin WaitzAug 3, 2006
  10. Sam VilainAug 3, 2006
  11. Blu CoraterAug 3, 2006
  12. Marc SingerAug 3, 2006
  13. Blu CoraterAug 3, 2006
  14. Marc SingerAug 3, 2006
  15. Francis DalyAug 3, 2006
  16. Marc SingerAug 4, 2006
  17. Francis DalyAug 4, 2006
  18. Marc SingerAug 4, 2006

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.