a6906d799f
An "[edit note]" link now appears next to "[add note]" whenever a line has shared notes: it presents the whole note blob in the input box for edition, and the save sends it as a replacement (the "setnotes" directive, carrying the hash of the blob the edit was based on). Emptying the box deletes the note. Clicking "add note" first and then "edit note" merges the reference notes with the pending addition so nothing typed so far is lost, and a "[cancel]" link aborts an edition opened by mistake without touching anything. An open input only disappears once its content is synchronized with the reference: a successful save, an update proving an exact match, or an explicit cancel. To that end, "Get updates" first silently closes the no-op boxes (opened but nothing changed), then after applying the fetched state it closes the boxes it made redundant (an addition someone already pushed, an edition matching the current notes), and re-bases an edition whose base moved, turning it red: red uniformly means "the reference changed under your edit, review the notes above against your text before saving". A save refused by the server (the "conflict <cid>" response lines) turns the input red the same way, keeping it in edition; states and additions from the same save are unaffected. After a reload, a browser-restored pending note reopens in append mode, the only safe assumption since a lost replacement base cannot be recovered. |
||
|---|---|---|
| .github | ||
| addons | ||
| admin | ||
| dev | ||
| doc | ||
| examples | ||
| include | ||
| reg-tests | ||
| scripts | ||
| src | ||
| tests | ||
| .gitattributes | ||
| .gitignore | ||
| .mailmap | ||
| .travis.yml | ||
| BRANCHES | ||
| BSDmakefile | ||
| CHANGELOG | ||
| CONTRIBUTING | ||
| INSTALL | ||
| LICENSE | ||
| MAINTAINERS | ||
| Makefile | ||
| README.md | ||
| SUBVERS | ||
| VERDATE | ||
| VERSION | ||
HAProxy
HAProxy is a free, very fast and reliable reverse-proxy offering high availability, load balancing, and proxying for TCP and HTTP-based applications.
Installation
The INSTALL file describes how to build HAProxy. A list of packages is also available on the wiki.
Getting help
The discourse and the mailing-list are available for questions or configuration assistance. You can also use the slack or IRC channel. Please don't use the issue tracker for these.
The issue tracker is only for bug reports or feature requests.
Documentation
The HAProxy documentation has been split into a number of different files for ease of use. It is available in text format as well as HTML. The wiki is also meant to replace the old architecture guide.
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)
License
HAProxy is licensed under GPL 2 or any later version, the headers under LGPL 2.1. See the LICENSE file for a more detailed explanation.