bernat at luffy.cx
Wed May 1 08:59:55 UTC 2013
Do you think this is a good idea to provide a default configuration file
for haproxy like this is currently done? I don't think this is:
1. We cannot provide sensible defaults.
2. We will have bugs about this file (like the one on syslog).
3. On each modification, the user will be prompted what to do on
upgrades while obviously she is not interested in keeping any
changes of the example.
I have no strong opinion, but I would suggest to remove this
configuration file. A user could start from one of the shipped
examples. Also, since we won't ship a configuration file by default, we
could remove the ENABLED variable from /etc/default/haproxy and only run
haproxy when there is a configuration file (we would still respect
ENABLED=0, in case the user choose to keep its /etc/default on upgrade).
panic("esp: what could it be... I wonder...");
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 835 bytes
Desc: not available
More information about the Pkg-haproxy-maintainers