|
From: | Andrew Gallagher |
Subject: | Re: Looking for peers for pgp.3t.al |
Date: | Mon, 6 Jan 2025 12:23:09 +0000 |
Hi, Etaoin. :-) On 6 Jan 2025, at 00:09, Etaoin Wu via SKS development and deployment list <sks-devel@nongnu.org> wrote:
Be careful to set the correct BEHIND* variables in haproxy, and that Caddy populates X-Forwarded-For -- otherwise haproxy may tarpit your entire Caddy instance. This is a commonly-encountered gotcha in the haproxy configuration. If you need help, please ask. :-)
It’s not a good idea to use the `master` branch in production, you should instead build from the current support branch `branch-2.2`. While changes in `master` have passed the unit tests, they are not production-ready; in particular, there may be sync and performance issues in `master` that will only become apparent once run in a full test cluster, which is done manually. Once you have the latest branch-2.2 running, you can add the pgpkeys.eu nodes as follows: # Andrew Gallagher <andrewg@andrewg.com> # 0x00CC54C6A0C601691AF4931FFB73E21AF1163937 [hockeypuck.conflux.recon.partner.fr_pgpkeys_eu] httpAddr="fr.pgpkeys.eu:11371" reconAddr="fr.pgpkeys.eu:11370" [hockeypuck.conflux.recon.partner.fi_pgpkeys_eu] httpAddr="fi.pgpkeys.eu:11371" reconAddr="fi.pgpkeys.eu:11370" [hockeypuck.conflux.recon.partner.de_pgpkeys_eu] httpAddr="de.pgpkeys.eu:11371" reconAddr="de.pgpkeys.eu:11370" A |
signature.asc
Description: Message signed with OpenPGP
[Prev in Thread] | Current Thread | [Next in Thread] |