Modularize apache config

[hennevogel]

We ship one file of apache config for everything as config(:noreplace). That configuration sets up some a tiny bit of dynamic variables that is adopted to the host and a large portion of static things that is the same on all hosts.

Now what people usually do is to change some of the dynamic parts. Then next time you do a package update you get a *.rpmnew file for this config. All is good.

Except if we want to touch the static part of the config. Like RewriteCond (17e8c2b) or even whole new features (a09bc3c).

We should put the parts that are host unspecific into files we Include into the dynamic part of the vhost config.

[adrianschroeter]

On Donnerstag, 30. Juli 2020, 18:21:24 CEST wrote Henne Vogelsang:

We ship one file of apache config for everything as `config(:noreplace)`. [That configuration](https://github.com/openSUSE/open-build-service/blob/master/dist/obs-apache24.conf) sets up some a tiny bit of dynamic variables that is adopted to the host and a large portion of static things that is the same on all hosts.

IMHO we can drop meanwhile the config for older apache2. That was for SLE 11 support which is no more...

…

Now what people usually do is to change some of the dynamic parts. Then next time you do a package update you get a *.rpmnew file for this config. All is good. Except if we want to touch the static part of the config. Like `RewriteCond` (17e8c2b) or even whole new features (a09bc3c). We should put the parts that are host unspecific into files we [`Include`](http://httpd.apache.org/docs/2.4/mod/core.html#include) into the dynamic part of the vhost config.

-- Adrian Schroeter email: adrian@suse.de SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany