[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: apache2: clearing the air [please read]

On Thu, Oct 11, 2001 at 10:13:00PM +1000, Daniel Stone wrote:
> The virtual host layout is such:
> 	* /var/www/the.host.name/htdocs - document root for that host
> 	* /var/www/the.host.name/cgi-bin - CGI scripts for that host
> 	* /var/www/the.host.name/logs - logs for that host

that's similar to my virtual host system for apache1 (and other
programs), except my system makes everything about a virtual host live
under a specific user's home directory:

/home/USER/public_html/LOGS/ -- .htaccess protected webalizer & analog stats
/home/USER/cgi-bin/common/ is a symlink to /usr/lib/cgi-bin/

one config file is used to:

1. maintain ip_alias addresses, by adding or deleting individual
ip_alias interfaces as required (NOT just blowing them all away and
recreating them from scratch - that takes several minutes or more
on a system with only a few hundred vhosts)

2. create config file fragments for apache (and other programs like
proftpd and htdig and linbot). it uses md5sum to detect whether a
particular vhost has had it's config fragment hand-edited.

3. do routine nightly/weekly processing for all vhosts - log file
rotation and web stats generation, linbot link checking, htdig indexing,

4. create summary pages listing details about all vhosts on the system

it's all completely automated. adding, changing, or deleting a vhost is
as simple as editing one file and running "make".

it works, and has been in production use on a number of servers (some
run by me, some run by other people) for a year or two now.

one of these days i'll package it for debian.


craig sanders <cas@taz.net.au>

Fabricati Diem, PVNC.
 -- motto of the Ankh-Morpork City Watch

Reply to: