It seems to me that if they put their application in /var/www/html (as opposed to /var/www/app/html), they they will not be able to run any other web applications on the server without conflicting with this one. Sure, they may say that they don't have plans to ever run any other applicaitons, but that's a very short-sighted view and they should understand that. At the very least they should understand that it is cheaper to add a web application to the same server than to be forced to purchase a new server for every application because of a short-sigted decision like this.
It also seems likely that they don't want to be responsible for managing the apache configuration, either because they either don't know how or they want you to be responsible if something goes wrong. A though situation to be in. On Fri, Oct 31, 2008 at 9:06 AM, Camron W. Fox <[EMAIL PROTECTED]> wrote: > Alle, > > They have asked, that we change the default directory > permission/ownership of /var/www/html,cgi-bin, instead of using the > Documentroot and ScriptAlias parameters in the apache configuration. > > > My question is: > > What argument, if any, would you use to try and convince the > customer > that this is a bad idea/bad practice? > > Best Regards, > Camron > > -- Perfection is just a word I use occasionally with mustard. --Atom Powers--
_______________________________________________ Discuss mailing list [email protected] http://lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
