I use Apache 2.2 in a few different environments.
- Development
In my development environment I use the Virtual Host Aliasing module to create a hassle-free multiple domain setup. This way, once configured I need to only create a directory for my site, and a DNS entry (or bonjour/avahi entry) to point to the proper DNS. This way, all of my sites, for example “pileofcrap.localhost” will automatically be parsed by apache and it will go to /var/www/pileofcrap/ as the document root. It’s handy, and I’ll post the config file here later. - Production
In my production environment I use a single config file per virtual host. This lets me set a granular configuration on a per site basis allowing for ultimate control. Since my production boxes are Ubuntu/Debian based, I also use the ‘a2ensite’ and ‘a2dissite’ with symlinks to the configurations to enable and disable.
Outside of Apache itself, I have a few automated scripts to run analytics on log files. Currently, I just use webalizer to process the logs. My script to do the analytics runs through every 6 hours. It checks my sites-enabled directory and parses each file for the Apache log settings and document root. It then runs and outputs to a stats folder in the document root making the analytics available and up to date on a regular basis.
To get runtime information, processes, memory usage, etc. I use some standard Munin plugins to poll my apache server on a regular basis and report back the usage.
That’s all for now, some more later.
