diff options
| author | Jason Little <realtyem@gmail.com> | 2023-07-11 13:08:06 -0500 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-07-11 13:08:06 -0500 |
| commit | 224ef0b669fdd85925d66deb38ba1b51c5aaa1bd (patch) | |
| tree | dcd4ecbaf195472a9ffb6319bd25cc5e60e2b59e /docs/workers.md | |
| parent | Add + as an allowed character for Matrix IDs (MSC4009) (#15911) (diff) | |
| download | synapse-224ef0b669fdd85925d66deb38ba1b51c5aaa1bd.tar.xz | |
Unix Sockets for HTTP Replication (#15708)
Unix socket support for `federation` and `client` Listeners has existed now for a little while(since [1.81.0](https://github.com/matrix-org/synapse/pull/15353)), but there was one last hold out before it could be complete: HTTP Replication communication. This should finish it up. The Listeners would have always worked, but would have had no way to be talked to/at. --------- Co-authored-by: Eric Eastwood <madlittlemods@gmail.com> Co-authored-by: Olivier Wilkinson (reivilibre) <oliverw@matrix.org> Co-authored-by: Eric Eastwood <erice@element.io>
Diffstat (limited to 'docs/workers.md')
| -rw-r--r-- | docs/workers.md | 9 |
1 files changed, 6 insertions, 3 deletions
diff --git a/docs/workers.md b/docs/workers.md index 828f082e75..735cd3f18d 100644 --- a/docs/workers.md +++ b/docs/workers.md @@ -95,9 +95,12 @@ for the main process * Secondly, you need to enable [redis-based replication](usage/configuration/config_documentation.md#redis) * You will need to add an [`instance_map`](usage/configuration/config_documentation.md#instance_map) -with the `main` process defined, as well as the relevant connection information from -it's HTTP `replication` listener (defined in step 1 above). Note that the `host` defined -is the address the worker needs to look for the `main` process at, not necessarily the same address that is bound to. +with the `main` process defined, as well as the relevant connection information from +it's HTTP `replication` listener (defined in step 1 above). + * Note that the `host` defined is the address the worker needs to look for the `main` + process at, not necessarily the same address that is bound to. + * If you are using Unix sockets for the `replication` resource, make sure to + use a `path` to the socket file instead of a `port`. * Optionally, a [shared secret](usage/configuration/config_documentation.md#worker_replication_secret) can be used to authenticate HTTP traffic between workers. For example: |