[plt-scheme] web-server reconfiguration

I have done this with a virtual host entry [1] that creates a
"my-application.server" virtual host entry, but leaves the 'localhost'
/ 'server' entry alone, so that the server can be managed normally,
while your application is resident in its own place.

This is only messy when you want your application to augment and/or
link to the defaults.

If you can think of a better way of specifying what you want, you
could write the configuration you'd like to write (please don't write
"(do-what-i-want)") and I can figure out how to make it work. A
potential idea is to allow paths/etc as a list of strings that are
checked in order (a left-masking union operator) rather than a single
string.

Jay

1. http://download.plt-scheme.org/doc/299.100/html/web-server/web-server.html#node_toc_node_sec_3.3

On 4/20/05, Geoffrey Knauth <geoff at knauth.org> wrote:
>   For list-related administrative tasks:
>   http://list.cs.brown.edu/mailman/listinfo/plt-scheme
> 
> I'm just starting with the PLT web server.  So far, it looks great.  I
> would like an arrangement like this:
> 
> A place for all the standard things that come with PLT, things that get
> (re)installed with every fresh version of PLT:
>      $PLTHOME/collects/web-server
> 
> A place for my files that I don't want overwritten and don't want to
> have to relocate on every version upgrade:
>      e.g., /any/old/path/web-server
> 
> In that latter place, I'd want to put my web-root:
>      e.g., conf/  htdocs/  log  passwords  servlets/
> 
> What's the cleanest way of doing this (or something similar)?  I looked
> at the docs, but I don't see a way to specify directories, only
> filenames.
> 
> Geoffrey
> --
> Geoffrey S. Knauth | http://knauth.org/gsk
> 
> 


-- 
Jay McCarthy <jay.mccarthy at gmail.com>
http://jay.makeoutcity.com/