Karl J. Runge wrote: > >Is it safe to say you do not want to run a 2nd instance of apache (with >a trimmed down config)? I.e. instead of just providing external >service on port 81, you also want to play around with new & different >webservers? >
Yeah, I tried a trimmed down version of apache and things got weird. I'm using the pre-built apache server that installs with debian's apt-get util. I suspect that there may be issues with how it is built. e.g. It seemed to ignore some of the directives I set in the trimmed down config file config file, like DocumentRoot - It kept serving up /var/www which is where the document root for the "normal" apache daemon (out of the box). Anyway, I concluded (perhaps prematurely) that: 1) I can build apache myself the way I want and make everything work. Then I won't be able to be lazy and type "apt-get upgrade" when I want a new version of apache. I'll have to actually do something. -or- 2) I can just use the stock apache daemon for the home network and find a different "minimal" web sever that is "orthoganal" to apache for the "Internet" and continue being lazy regarding my apache daemon. I wonder, is there a way to tell apache to use a different document root depending on the port? That would be cool way for sorting it out. -Andrew Gaunt ***************************************************************** To unsubscribe from this list, send mail to [EMAIL PROTECTED] with the text 'unsubscribe gnhlug' in the message body. *****************************************************************
