I have to admit my point of view focuses on more generic cases rather than extreme cases like the one you describe with "hundreds of virtualhosts".
2017-09-18 20:03 GMT+02:00 Reindl Harald <h.rei...@thelounge.net>: > > > Am 18.09.2017 um 19:28 schrieb Daniel: >> >> I see >> >> But we already have a handy directive to avoid repetition when >> necessary, a directive that btw many distros abuse, "Include". You >> define the common parts in a single file and Include the appropiate >> file. > > > that scales bad when the vhost itself is already one of hundrets of Includes > > i have currently written/refactored a "config parser" for vhosts with > support of some comments to configure Letsencrypt tasks as well as generate > the remap/ssl config of a reverse proxy, based on some Alias-statements > webstats shellscripts are generated and the whole hosting database is feeded > with that data too > > that works independent of the number of hosts, a shellscript on the > admin-servers fetchs all config file sof all webservers and from there the > central proxy configuration is feeded > > well, in other word, with some lines of code based on apache vhost includes > the whole company is driven and implement includs support here would be at > least dangerous and hard to test since that all runs over many machines and > testing environments >
