Bug#272340: apache2 compatibility problems.

[Ryan Hayle <hackel@walkingfish.com>]

ogi,
I don't understand your symlink:

# ln -s . /etc/apache2/conf

Are you saying the webmin-apache module looks for a "conf" directory
within the apache server root?  Where did you run into this?


Jaldhar,

Is the package indeed orphaned or are you thinking of picking it up
again?

The biggest issue I see is that webmin-apache doesn't support Debian's
apache2 configuration layout:
 module directives in /etc/apache2/mods-available
 virtual servers in /etc/apache2/sites-available
plus symlinks to enable each in mods-enabled and sites-enabled.

Also, the module is looking for access.conf and srm.conf which are no
longer used.  I'm guessing it doesn't parse the files
in /etc/apache2/conf.d either, but only the master apache2.conf.

After I first changed my webmin-apache module configuration (as ogi
described), the module said my configuration had changed and promtped me
to "re-configure known modules", however it had only defaulted to those
which were enabled in apache2.conf, NOT those enabled
in /etc/apache2/mods-enabled (ssl, php4, etc.).  I selected those
manually, 

Adding a virtual domain doesn't work either.  If I set the virtual
servers directory to /etc/apache2/sites-available, then the new domain
is created in e.g. /etc/apache2/sites-available/test.com.conf, however
once it's created it disappears.  Webmin never re-reads that file again,
so it doesn't show up under "Virtual Servers".  Also, webmin doesn't
symlink that file to /etc/apache2/sites-enabled, nor provide any way to
enable it.

Most of these problems can be avoided by using a monolithic apache 1.x
configuration scheme, however this is not desirable in my mind, as
Debian's scheme is most brilliant.  I have not investigated the webmin
lists to see if any of this is under active development, but I do hope
it will be available soon.

Thanks,
Ryan Hayle