I don’t yet know enough to ask about this, but that’s not going to stop me
I know we have a box where, in addition to serving bk:// on the expected port, we also run a bkd on port 80, for folks who want to look at repos using a web browser.
This works fine for our BK servers that are directly connected to the internet.
The trick is we want to deploy these boxes on a DMZ network, which is accessed thru an haproxy box.
haproxy does frontend checks on the incoming packet (in this case, http or https) to check the header information to identify the host that the client wants to talk to. Cool. We’re in the process of learning how haproxy can get packets from other ports, specifically for BK, and when we get these packets we’re going to want to see how haproxy can poke in the packet header enough to figure out what hostname the client is trying to reach, so we can redirect the traffic to the appropriate back-end BK server on the DMZ network.
Got any suggestions for me?