Perforce
guest@6admin.io:~$ ls ~/tags/perforce
A reverse proxy in front of Perforce, or not: the pros and cons
Four ways to put TLS in front of a Perforce server and what each one costs: nginx layer-4 termination, p4d native TLS, SNI passthrough and the in-house tools P4Broker and P4P. With the client-IP trap everyone forgets.
Nginx in front of Perforce: layer-4 TLS termination and the P4 protocol
Putting nginx in TLS termination in front of a Perforce server: why the stream module and not an HTTP proxy, what the P4 protocol imposes and the keepalive and timeout tuning without which long sessions get cut on multi-hour syncs.
Nginx on Windows in front of Jenkins: the proxy, the logs and the upgrades
Nginx on Windows Server terminating TLS in front of Jenkins: the UI and the WebSocket agents in a single location, the certificate through simple-acme and above all the two operational nuisances nobody writes about on Windows, log rotation and the Chocolatey upgrade.