{"id":421,"date":"2015-02-01T16:25:38","date_gmt":"2015-02-01T15:25:38","guid":{"rendered":"http:\/\/lazic.info\/josip\/?p=421"},"modified":"2016-05-05T15:38:14","modified_gmt":"2016-05-05T14:38:14","slug":"splitting-haproxy-config","status":"publish","type":"post","link":"https:\/\/lazic.info\/josip\/post\/splitting-haproxy-config\/","title":{"rendered":"Splitting monolithic HAProxy configuration into more manageable form"},"content":{"rendered":"

As soon as you have more than a few frontend, backend and listen directives in your HAProxy config thing get crowded in that single monolithic file. There are few possible solutions to this “problem”, like this python solution<\/a>, or maybe using multiple config files and specifying them with -f when starting haproxy (http:\/\/comments.gmane.org\/gmane.comp.web.haproxy\/5888<\/a>).<\/p>\n

While there is nothing wrong with above mentioned solutions I think there is a better aproach where script would check if new configuration is valid before restarting HAProxy. Script below assumes you have colordiff, and etckeeper<\/a> installed and configured. If you don’t you should think about using etckeeper, it can save you from trouble when you need to revert some changes in \/etc directory.
\n<\/p>\n

First create \/etc\/haproxy\/conf.d\/ and split your haproxy.cfg in multiple files prefixed with numbers in order in which you would like them to be in final config. IE. in 00-global.cfg<\/em> put your global options, and in 99-global.cfg<\/em> put everything you want at the end of final HAProxy config file. If you need to disable one site simple rename it into 11-site1.cfg.disable, and run this script: https:\/\/gist.github.com\/jlazic\/e65f5bda141ffaed5640<\/a>.<\/p>\n