[Mageia-dev] changing apache configuration handling

Renaud MICHEL r.h.michel+mageia at gmail.com
Thu Sep 15 00:34:39 CEST 2011


Hello
On mercredi 14 septembre 2011 at 10:06, Guillaume Rousse wrote :
> So, we have the following choice:
> - change current behaviour, by keeping conditionals in configuration 
> file. To use php, you have to install mod_php, and add -DHAVE_PHP5 in 
> /etc/sysconfig/httpd. This means additional configuration is required, 
> but also possibility to temporary disable without uninstalling.
> 
> - keep current behaviour, by removing conditionals in configuration 
> file. This means no additional configuration needed, but also than 
> installing implies usage.

How about the way it works on debian?

Their apache2.2-common package, which contains all the base configuration 
files, has a mods-available and a mods-enabled dirs in the apache conf dir 
(/etc/apache2 for debian).
Modules load command and specific configuration (if needed) are provided as 
*.load and *.conf files in the mods-available dir, then the a2enmod command 
is used to enable (and its counterpart e2dismod disables them) some mods by 
creating symlink in the mods-enabled dir.
The main apache2.conf file then has
Include mods-enabled/*.load
Include mods-enabled/*.conf
to load the actually enabled mods.
a2enmod also knows about modules dependencies via special comments in the 
*.load files.

Then there is a similar mechanism for sites installed by packages with 
sites-available and sites-enabled directories and a2ensite a2dissite 
commands.

see
http://packages.debian.org/squeeze/apache2.2-common
http://manpages.debian.net/cgi-bin/man.cgi?query=A2ENMOD
http://manpages.debian.net/cgi-bin/man.cgi?query=A2ENSITE

-- 
Renaud Michel


More information about the Mageia-dev mailing list