Yeah, this is an ideal way to go. Althought, depending to what degree you can trust your developers (contractors, etc.) and how much your sys admins want to admin it may or may not be a good fit.
> > We have a similar issue here but it is designed more for development of > > modules/code by multiple developers. > > If each of your developers runs her own copy of Apache, each copy > listening to a different port, you can make the namespace collision > problems go away. Use a common httpd.conf for all developers with a > small section specifically for each one, and start Apache separately > for each developer with '-Ddeveloperid'. You can trade off between > the isolation of multiple copies of the complete site(s) on the one > machine, and the fun of sharing some of the code/data. I'd keep it > all separate, discs are cheap enough. > > <IfDefine ged> > User ged > Port 8011 > ErrorLog /home/ged/apache/error_log > PidFile /tmp/ged.pid > LockFile /tmp/... > DocumentRoot ... > </IfDefine> > > <IfDefine stas> > User stas > Port 8012 > ErrorLog /home/stas/apache/error_log > PidFile /tmp/stas.pid > LockFile /tmp/... > DocumentRoot ... > </IfDefine>
