diff options
| author | DMRobertson <DMRobertson@users.noreply.github.com> | 2021-11-01 11:36:20 +0000 |
|---|---|---|
| committer | DMRobertson <DMRobertson@users.noreply.github.com> | 2021-11-01 11:36:20 +0000 |
| commit | 6b78680875d9e721d46e4f3d34047c6a3fbd2f33 (patch) | |
| tree | d64455b2305504485a55d2fec294620c72e6398d /develop/workers.html | |
| parent | deploy: e320f5dba32f5b5818b6d5a0059ae388430b9a72 (diff) | |
| download | synapse-6b78680875d9e721d46e4f3d34047c6a3fbd2f33.tar.xz | |
deploy: ece84f2c450d986e54acc80971225fb02f4e1d05
Diffstat (limited to 'develop/workers.html')
| -rw-r--r-- | develop/workers.html | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/develop/workers.html b/develop/workers.html index 44b2ceab18..e33576bfc9 100644 --- a/develop/workers.html +++ b/develop/workers.html @@ -531,16 +531,16 @@ media repository. Note that doing so will prevent the main process from being able to handle the above endpoints.</p> <p>In the <code>media_repository</code> worker configuration file, configure the http listener to expose the <code>media</code> resource. For example:</p> -<pre><code class="language-yaml"> worker_listeners: - - type: http - port: 8085 - resources: - - names: - - media +<pre><code class="language-yaml">worker_listeners: + - type: http + port: 8085 + resources: + - names: + - media </code></pre> <p>Note that if running multiple media repositories they must be on the same server and you must configure a single instance to run the background tasks, e.g.:</p> -<pre><code class="language-yaml"> media_instance_running_background_jobs: "media-repository-1" +<pre><code class="language-yaml">media_instance_running_background_jobs: "media-repository-1" </code></pre> <p>Note that if a reverse proxy is used , then <code>/_matrix/media/</code> must be routed for both inbound client and federation requests (if they are handled separately).</p> <h3 id="synapseappuser_dir"><a class="header" href="#synapseappuser_dir"><code>synapse.app.user_dir</code></a></h3> @@ -567,7 +567,7 @@ endpoints matching the following regular expressions:</p> must therefore be configured with the location of the main instance, via the <code>worker_main_http_uri</code> setting in the <code>frontend_proxy</code> worker configuration file. For example:</p> -<pre><code>worker_main_http_uri: http://127.0.0.1:8008 +<pre><code class="language-yaml">worker_main_http_uri: http://127.0.0.1:8008 </code></pre> <h3 id="historical-apps"><a class="header" href="#historical-apps">Historical apps</a></h3> <p><em>Note:</em> Historically there used to be more apps, however they have been |