On 6/5/23 01:41, Artur wrote:
What is suggested/recommended way to get QUIC / HTTP/3 working in
haproxy on Debian ?
I have been debating for a while whether or not to get the work I have
done on build scripts out into the world. Just mirrored the repo from
my gitlab server to github, so have fun with it!
https://github.com/elyograg/haproxy-scripts
I happened to have a debian 11 VM, i386 architecture. I tested the
scripts there with these steps:
mkdir ~/git
cd ~/git
sudo apt-y install git
git clone https://github.com/elyograg/haproxy-scripts.git
cd haproxy-scripts
./prep-source
sudo mkdir -p /etc/haproxy
./install-haproxy-service git-haproxy-2.8
./fullstack
They're shell scripts, so there is no mystery about what they do.
The prep_source script will install a whole lot of packages ...
compilers, libraries needed for the compile, and some other tools.
The "repo_overrides" file is pre-setup to force a specific branch of
quictls. If you remove that, it will get the newest 3.1.x branch that
ends in +quic.
The scripts do not attempt to install /etc/haproxy/haproxy.cfg ... you
will have to handle that. You can use the `ci-haproxy-cfg.txt` file as
a starting point for your own config. It's the barebones config that I
use for the gitlab CI job I built. It uses a self-signed certificate
that is also included but not copied by default to the right directory
for the config.
The scripts that compile the software will figure out how many physical
CPU cores you have, divide that by 2, then set the number of threads for
`make` to that value or a minimum value of 3.
This means the scripts have been tested on Ubuntu, Debian, and CentOS 7,
and were found to work on all 3.
Thanks,
Shawn
