matrix-docker-ansible-deploy/roles/custom/matrix-synapse-reverse-proxy-companion
Slavi Pantaleev 1c68fd0d9b Make matrix-synapse-reverse-proxy-companion not report "502 Bad Gateway" when Synapse workers restart
Since nginx 1.27.3, we can make use of the `resolve` parameter for an `upstream`'s `server`,
to allow DNS resolution to happen continuously at runtime, not just once during startup.

Previously, this was not possible to do in an `upstream` block without
an nginx-plus subscription. Outside of an `upstream` block, we've used
and still use `set $backend ..` workarounds to get DNS resolution at
runtime, but now we can do it in `upstream` as well.
2025-03-05 21:24:43 +02:00
..
defaults Add license information to files for matrix-synapse-reverse-proxy-companion 2025-03-03 00:18:04 +09:00
tasks Add license information to files for matrix-synapse-reverse-proxy-companion 2025-03-03 00:18:04 +09:00
templates Make matrix-synapse-reverse-proxy-companion not report "502 Bad Gateway" when Synapse workers restart 2025-03-05 21:24:43 +02:00