Michael C. Neel
neel at mediapulse.com
Mon Nov 10 15:22:59 EST 2003
> > Without wanting to sound flippy or anything like that, but, > I don't see > > much sense in such a configuration-time parameter "automatization", > > because, setting such parameters is part of any deployment, > it's better > > to keep things explicit, no? > > Not necessarily. Developing Web applications in a team environment > often entails having developers running multiple instances of the > server, each running within the user's context and bound to his own > port. In situations like this, doing run-time > paramaterization is critical. > > But yes, for production applications it might make less sense. Would each be under his own virtual server in apache then, and therefore have his own config section? This just seems to be saving some typing the the httpd.conf file, a few lines above the PythonOption will be DocumentRoot. mod_perl goes insane and allows programming logic in the conf file, and this is a bad thing imho; nothing like restarting a server that doesn't come back because of a programmin error inside the conf and quickly trying to debug it while the entire server remains down. Mike
|