mirror of
http://git.haproxy.org/git/haproxy.git
synced 2026-02-11 05:03:05 +02:00
49c2b45c1d
Let's apply the fuzzy match to server keywords so that we can avoid dumping the huge list of supported keywords each time there is a spelling mistake, and suggest proper spelling instead: $ printf "listen f\nserver s 0 sendpx-v2\n" | ./haproxy -c -f /dev/stdin [NOTICE] 070/095718 (24152) : haproxy version is 2.4-dev11-caa6e3-25 [NOTICE] 070/095718 (24152) : path to executable is ./haproxy [ALERT] 070/095718 (24152) : parsing [/dev/stdin:2] : 'server s' unknown keyword 'sendpx-v2'; did you mean 'send-proxy-v2' maybe ? [ALERT] 070/095718 (24152) : Error(s) found in configuration file : /dev/stdin [ALERT] 070/095718 (24152) : Fatal errors found in configuration.
The HAProxy documentation has been split into a number of different files for ease of use. Please refer to the following files depending on what you're looking for : - INSTALL for instructions on how to build and install HAProxy - BRANCHES to understand the project's life cycle and what version to use - LICENSE for the project's license - CONTRIBUTING for the process to follow to submit contributions The more detailed documentation is located into the doc/ directory : - doc/intro.txt for a quick introduction on HAProxy - doc/configuration.txt for the configuration's reference manual - doc/lua.txt for the Lua's reference manual - doc/SPOE.txt for how to use the SPOE engine - doc/network-namespaces.txt for how to use network namespaces under Linux - doc/management.txt for the management guide - doc/regression-testing.txt for how to use the regression testing suite - doc/peers.txt for the peers protocol reference - doc/coding-style.txt for how to adopt HAProxy's coding style - doc/internals for developer-specific documentation (not all up to date)