mirrors/synapse
1
0
Fork 0
mirror of https://github.com/element-hq/synapse.git synced 2024-11-24 18:45:52 +03:00
Code Issues Projects Releases Packages Wiki Activity

Keep pointing at packages.matrix.org for now

Browse source
This commit is contained in:
Erik Johnston 2023-12-13 15:18:58 +00:00
parent 95f0a53662
commit 188a51daa9
2 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
.github/ISSUE_TEMPLATE/BUG_REPORT.yml vendored
View file

@ -71,7 +71,7 @@ body:
label: Installation Method label: Installation Method
options: options:
- Docker (matrixdotorg/synapse) - Docker (matrixdotorg/synapse)
- Debian packages from packages.element.io - Debian packages from packages.matrix.org
- pip (from PyPI) - pip (from PyPI)
- Other (please mention below) - Other (please mention below)
- I don't know - I don't know

6
docs/workers.md
View file

@ -62,7 +62,7 @@ pip install "matrix-synapse[redis]"
Note that these dependencies are included when synapse is installed with `pip Note that these dependencies are included when synapse is installed with `pip
install matrix-synapse[all]`. They are also included in the debian packages from install matrix-synapse[all]`. They are also included in the debian packages from
`packages.element.io` and in the docker images at `packages.matrix.org` and in the docker images at
https://hub.docker.com/r/ectorim/synapse/. https://hub.docker.com/r/ectorim/synapse/.
To make effective use of the workers, you will need to configure an HTTP To make effective use of the workers, you will need to configure an HTTP
@ -94,7 +94,7 @@ file suitable for use with workers:
for the main process for the main process
* Secondly, you need to enable * Secondly, you need to enable
[redis-based replication](usage/configuration/config_documentation.md#redis) [redis-based replication](usage/configuration/config_documentation.md#redis)
* You will need to add an [`instance_map`](usage/configuration/config_documentation.md#instance_map) * 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 with the `main` process defined, as well as the relevant connection information from
it's HTTP `replication` listener (defined in step 1 above). 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` * Note that the `host` defined is the address the worker needs to look for the `main`
@ -432,7 +432,7 @@ To enable this, the worker must have:
* An [HTTP `replication` listener](usage/configuration/config_documentation.md#listeners) configured, * An [HTTP `replication` listener](usage/configuration/config_documentation.md#listeners) configured,
* Have a [`worker_name`](usage/configuration/config_documentation.md#worker_name) * Have a [`worker_name`](usage/configuration/config_documentation.md#worker_name)
and be listed in the [`instance_map`](usage/configuration/config_documentation.md#instance_map) and be listed in the [`instance_map`](usage/configuration/config_documentation.md#instance_map)
config. config.
* Have the main process declared on the [`instance_map`](usage/configuration/config_documentation.md#instance_map) as well. * Have the main process declared on the [`instance_map`](usage/configuration/config_documentation.md#instance_map) as well.
Note: The same worker can handle multiple streams, but unless otherwise documented, Note: The same worker can handle multiple streams, but unless otherwise documented,