On 11/5/2023 02:48, Christoph Kukulies wrote:
I git cloned haproxy and compiled it :
root@mail:~/haproxy# ./haproxy --version
HAProxy version 2.9-dev8-ce7501-38 2023/11/04 - https://haproxy.org/
<https://haproxy.org/>
Status: development branch - not safe for use in production.
Known bugs: https://github.com/haproxy/haproxy/issues?q=is:issue+is:open
<https://github.com/haproxy/haproxy/issues?q=is:issue+is:open>
Running on: Linux 5.15.0-88-generic #98-Ubuntu SMP Mon Oct 2 15:18:56
UTC 2023 x86_64
Usage : haproxy [-f <cfgfile|cfgdir>]* [ -vdVD ] [ -n <maxconn> ] [ -N
<maxpconn> ]
Probably this is not what I want? Better 2.8 stable?
I compiled with
make TARGET=linux-glibc
Many projects have a single git repo for all versions and use branches
to separate them. Haproxy doesn't. 2.8 is developed in a completely
separate git repository from the one that you cloned. This is the repo
that you want:
https://git.haproxy.org/git/haproxy-2.8.git
My scripts just make things easier. They will compile/install haproxy
2.8 and the latest 3.1.x version of quictls/openssl (currently 3.1.4)
with only a few commands. The repo does not contain binaries ... all
scripts can be examined to verify that nothing shady is happening.
Today I pushed up some fixes.
The quictls repo is a fork of openssl, which has been patched to include
QUIC functions that haproxy can use to provide QUIC/HTTP3:
https://github.com/quictls/openssl
Thanks,
Shawn
