On 22 May 2002, Jonathan Corbet said:
> Step one was, for the relevant virtual host:
>
>       DocumentRoot .../www/lwn/lwn.py
>
> That is, of course, the famous "driver script" - but it never gets run.
> It's just a way of forcing the server to move down into the "lwn"
> directory, where a special regime is in force:

Hmmm, interesting.  Maybe even sneaky.  How do you deal with images and
other stuff that don't have to involve Quixote?  Just let 'em go through
Quixote and never mind the overhead?  Or do you have a separate server?

As long as we're comparing configurations, here's what
www.mems-exchange.org does for the bulk of the site:


    SCGIServer 127.0.0.1 3000
    SCGIHandler On


That tedious regex is just the list of top-level "directories" handled
by Quixote, so eg.

  http://www.mems-exchange.org/account/

is handled by the SCGI server on port 3000 (our driver script), while

  http://www.mems-exchange.org/images/logo-medium.gif

is handled directly by Apache by going straight to the filesystem.

However, that's not the only Quixote app running on this server -- we
also have SPLAT! (a bug tracker) running at /bugs/:

  RewriteRule ^/bugs$ /bugs/ [redirect=permanent]
  RewriteRule ^/bugs(.*) /www/cgi-bin/splat.fcgi$1 [l]

I haven't bothered with SCGI for SPLAT! -- it seems to work just fine
with FastCGI.

        Greg