On Mon, Aug 19, 2002 at 04:12:55PM +0100, Matt Kern wrote:
> I can see the advantages of all the separate configuration
> directories, but cannot see quite how everything fits together. I
> understand the include mechanism and most of the files under
> /etc/apache2, but where are the referred to binaries addhost,
> ap2addhost and a2enhost (or whatever they are called in the files and
> postings I have read)? I can't find anything on my system that makes
> use of the *.d directories in /etc/vhost.
apache2 packages will include all files from /etc/apache2-enabled/ and
generate vhosts with the configs in /etc/apache2/sites-enabled/.
You basically use the /etc/apache2/mods-available/ files as templates. there
is a load directive and some config stuff. the a2enmod is simply moving the
files from the avbailable dir into the enabled dir. It is a simple readable
shell script and i dont think it is a good idea to have them lay around and
clutter the namespace.
I dont know about the vhost stuff besides the site dir.
> Have I caught the apache2 package in a state of extreme development?
the packages are pretty new, but working well for me.
- From: Matt Kern <email@example.com>