I'm configuring Apache under a Debian based Linux distribution. I would like to configure it in such a way that my configuration changes don't get in the way of Apache upgrades. I would like to do it in such a way that I don't have to edit any of the configuration files that come with the distribution.
I know that I can put the configuration for my websites in the /etc/apache2/sites-available directory and then enable them with
a2ensite. Similarly, I can enable the modules I want with
What happens if I write new configuration files into /etc/apache2/conf-available/ and then use
a2enconf to enable them? Specifically, will the be able to override settings that are specified in other configuration files. For example /etc/apache2/apache2.conf specifies
Timeout 300. If I put
Timeout 500 in my configuration file, will it override the earlier declaration? Would there be any Apache configuration directives for which using this override technique would not work?