Slavi Pantaleev 4d62a75f6f Get matrix-corporal to play nicely with a Synapse worker setup ... We do this by creating one more layer of indirection. First we reach some generic vhost handling matrix.DOMAIN. A bunch of override rules are added there (capturing traffic to send to ma1sd, etc). nginx-status and similar generic things also live there. We then proxy to the homeserver on some other vhost (only Synapse being available right now, but repointing this to Dendrite or other will be possible in the future). Then that homeserver-specific vhost does its thing to proxy to the homeserver. It may or may not use workers, etc. Without matrix-corporal, the flow is now: 1. matrix.DOMAIN (matrix-nginx-proxy/matrix-domain.conf) 2. matrix-nginx-proxy/matrix-synapse.conf 3. matrix-synapse With matrix-corporal enabled, it becomes: 1. matrix.DOMAIN (matrix-nginx-proxy/matrix-domain.conf) 2. matrix-corporal 3. matrix-nginx-proxy/matrix-synapse.conf 4. matrix-synapse (matrix-corporal gets injected at step 2).		2021-01-25 09:46:41 +02:00
..
conf.d	Get matrix-corporal to play nicely with a Synapse worker setup	2021-01-25 09:46:41 +02:00
matrix-synapse-metrics-htpasswd.j2	Fix indentation in templates	2019-05-07 21:23:35 +02:00
nginx.conf.j2	add option to disable nginx access log	2020-12-21 21:26:49 +01:00