Annika Wickert wrote: > - Include possibility in configfile to maintain one configfile for each > backend / frontend pair
There are several scripts out there which concat files in a well-known directory structure together to form a single final config file. These can be used in your init script just before starting HAProxy itself. I found this approach very versatile as it allows me to structure my configs the way I want. The only thing that doesn't easily work with this approach is to include one file in multiple places, although that too could be solved with symlinks. And I never actually missed that functionality. Finally, HAProxy accepts multiple -f arguments arguments to load multiple files in its own. --Holger [1] https://github.com/meineerde-cookbooks/haproxy/blob/master/files/default/haproxy_join [2] https://github.com/joewilliams/haproxy_join [3] https://github.com/finnlabs/haproxy/blob/master/haproxy-config.py
