On 19 November 2011 16:23, Olivier Beaton olivier.beaton@gmail.com wrote:
And it should be noted that all you rename in debian-apache are softlinks in the mods-enabled and sites-enabled directories. You would keep regular non-prefixed filenames in mods-available and sites-available. Using this method you could also allow some of your users to own the files themselves (although this is a security risk, you may want to install a panel if you have many users).
I was interested by the fact that Wikimedia, running a config for hundreds of largely identical Apaches on Ubuntu, *does not* in fact do things the Debian way, but loads the modules in an httpd.conf file just like every other Unix/Linux distro does it.
I'd always thought the Debian way was too ridiculously fiddly to scale efficiently. I'm sure there are ways to, but it's entirely unclear how doing it the Debian way is actually better for the job than doing it with a single simple config file.
The way we do it at work, with several almost-but-not-quite-identical Ubuntu servers, is directly inspired by the way Wikimedia do it: /etc/apache2/conf.d/ has 00-httpd.conf with our standard module config in it (identical for all), 01-vhost-default.conf with box-specific details, and a series of files with names matching vhost-*.conf for each virtual host. (And since mod_jk doesn't have a Debian/Ubuntu package, I rolled one myself that adds an 01-mod-jk.conf file in the same directory to load itself and configure JkMount, for the boxes that need that.)
- d.