From 9f273f34d4ac64ef9d47721b04187ed273fc998d Mon Sep 17 00:00:00 2001 From: erikjohnston Date: Thu, 29 Jul 2021 10:09:19 +0000 Subject: deploy: c36c2777900284cf94e93e60e34c3b856bb31551 --- latest/workers.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'latest/workers.html') diff --git a/latest/workers.html b/latest/workers.html index 6522f27c60..919a6ee90a 100644 --- a/latest/workers.html +++ b/latest/workers.html @@ -237,7 +237,7 @@ https://hub.docker.com/r/matrixdotorg/synapse/.

To make effective use of the workers, you will need to configure an HTTP reverse-proxy such as nginx or haproxy, which will direct incoming requests to the correct worker, or to the main synapse instance. See -reverse_proxy.md for information on setting up a reverse +the reverse proxy documentation for information on setting up a reverse proxy.

When using workers, each worker process has its own configuration file which contains settings specific to that worker, such as the HTTP listener that it @@ -312,8 +312,8 @@ endpoints to the worker (localhost:8083 in the above example).

synctl or your distribution's preferred service manager such as systemd. We recommend the use of systemd where available: for information on setting up systemd to start synapse workers, see -systemd-with-workers. To use synctl, see -synctl_workers.md.

+Systemd with Workers. To use synctl, see +Using synctl with Workers.

Available worker applications

synapse.app.generic_worker

This worker can handle API requests matching the following regular -- cgit 1.5.1