mirror of
https://git.haproxy.org/git/haproxy.git/
synced 2026-02-08 19:01:19 +01:00
b01302f9ac
We've been emitting warnings for over 5 years (since 1.5-dev22) about configs accidently carrying multiple servers with the same name in the same backend, and this starts to cause some real trouble in dynamic environments since it's still very difficult to accurately process a state-file and we still can't transport a server's name over the peers protocol because of this. It's about time to force users to fix their configs if they still hadn't given that there is zero technical justification for doing this, beyond the "yyp" (or copy-paste accident) when editing the config. The message remains as clear as before, indicating the file and lines of the conflict so that the user can easily fix it.
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 - 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)