Matrix/synapse
Matrix/synapse
1
0
Fork 0
mirror of https://github.com/element-hq/synapse synced 2024-09-30 03:32:41 +00:00
Code Issues Projects Releases Packages Wiki Activity

deploy: 62d8b0361b

Browse source
This commit is contained in:
anoadragon453 2024-07-09 15:44:30 +00:00
parent e543fddc2a
commit bf33ed4826
5 changed files with 10 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
v1.111/print.html
View file

@ -1853,10 +1853,11 @@ each upgrade are complete before moving on to the next upgrade, to avoid
stacking them up. You can monitor the currently running background updates with stacking them up. You can monitor the currently running background updates with
<a href="usage/administration/admin_api/background_updates.html#status">the Admin API</a>.</p> <a href="usage/administration/admin_api/background_updates.html#status">the Admin API</a>.</p>
<h1 id="upgrading-to-v11110"><a class="header" href="#upgrading-to-v11110">Upgrading to v1.111.0</a></h1> <h1 id="upgrading-to-v11110"><a class="header" href="#upgrading-to-v11110">Upgrading to v1.111.0</a></h1>
<h2 id="new-worker-endpoints-for-authenticated-client-media"><a class="header" href="#new-worker-endpoints-for-authenticated-client-media">New worker endpoints for authenticated client media</a></h2> <h2 id="new-worker-endpoints-for-authenticated-client-and-federation-media"><a class="header" href="#new-worker-endpoints-for-authenticated-client-and-federation-media">New worker endpoints for authenticated client and federation media</a></h2>
<p><a href="./workers.html#synapseappmedia_repository">Media repository workers</a> handling <p><a href="./workers.html#synapseappmedia_repository">Media repository workers</a> handling
Media APIs can now handle the following endpoint pattern:</p> Media APIs can now handle the following endpoint patterns:</p>
<pre><code>^/_matrix/client/v1/media/.*$ <pre><code>^/_matrix/client/v1/media/.*$
^/_matrix/federation/v1/media/.*$
</code></pre> </code></pre>
<p>Please update your reverse proxy configuration.</p> <p>Please update your reverse proxy configuration.</p>
<h1 id="upgrading-to-v11060"><a class="header" href="#upgrading-to-v11060">Upgrading to v1.106.0</a></h1> <h1 id="upgrading-to-v11060"><a class="header" href="#upgrading-to-v11060">Upgrading to v1.106.0</a></h1>
@ -12013,6 +12014,7 @@ worker_log_config: /etc/matrix-synapse/federation-sender-log.yaml
<p>Handles the media repository. It can handle all endpoints starting with:</p> <p>Handles the media repository. It can handle all endpoints starting with:</p>
<pre><code>/_matrix/media/ <pre><code>/_matrix/media/
/_matrix/client/v1/media/ /_matrix/client/v1/media/
/_matrix/federation/v1/media/
</code></pre> </code></pre>
<p>... and the following regular expressions matching media-specific administration APIs:</p> <p>... and the following regular expressions matching media-specific administration APIs:</p>
<pre><code>^/_synapse/admin/v1/purge_media_cache$ <pre><code>^/_synapse/admin/v1/purge_media_cache$

2
v1.111/searchindex.js
View file

File diff suppressed because one or more lines are too long

2
v1.111/searchindex.json
View file

File diff suppressed because one or more lines are too long

5
v1.111/upgrade.html
View file

@ -286,10 +286,11 @@ each upgrade are complete before moving on to the next upgrade, to avoid
stacking them up. You can monitor the currently running background updates with stacking them up. You can monitor the currently running background updates with
<a href="usage/administration/admin_api/background_updates.html#status">the Admin API</a>.</p> <a href="usage/administration/admin_api/background_updates.html#status">the Admin API</a>.</p>
<h1 id="upgrading-to-v11110"><a class="header" href="#upgrading-to-v11110">Upgrading to v1.111.0</a></h1> <h1 id="upgrading-to-v11110"><a class="header" href="#upgrading-to-v11110">Upgrading to v1.111.0</a></h1>
<h2 id="new-worker-endpoints-for-authenticated-client-media"><a class="header" href="#new-worker-endpoints-for-authenticated-client-media">New worker endpoints for authenticated client media</a></h2> <h2 id="new-worker-endpoints-for-authenticated-client-and-federation-media"><a class="header" href="#new-worker-endpoints-for-authenticated-client-and-federation-media">New worker endpoints for authenticated client and federation media</a></h2>
<p><a href="./workers.html#synapseappmedia_repository">Media repository workers</a> handling <p><a href="./workers.html#synapseappmedia_repository">Media repository workers</a> handling
Media APIs can now handle the following endpoint pattern:</p> Media APIs can now handle the following endpoint patterns:</p>
<pre><code>^/_matrix/client/v1/media/.*$ <pre><code>^/_matrix/client/v1/media/.*$
^/_matrix/federation/v1/media/.*$
</code></pre> </code></pre>
<p>Please update your reverse proxy configuration.</p> <p>Please update your reverse proxy configuration.</p>
<h1 id="upgrading-to-v11060"><a class="header" href="#upgrading-to-v11060">Upgrading to v1.106.0</a></h1> <h1 id="upgrading-to-v11060"><a class="header" href="#upgrading-to-v11060">Upgrading to v1.106.0</a></h1>

1
v1.111/workers.html
View file

@ -792,6 +792,7 @@ worker_log_config: /etc/matrix-synapse/federation-sender-log.yaml
<p>Handles the media repository. It can handle all endpoints starting with:</p> <p>Handles the media repository. It can handle all endpoints starting with:</p>
<pre><code>/_matrix/media/ <pre><code>/_matrix/media/
/_matrix/client/v1/media/ /_matrix/client/v1/media/
/_matrix/federation/v1/media/
</code></pre> </code></pre>
<p>... and the following regular expressions matching media-specific administration APIs:</p> <p>... and the following regular expressions matching media-specific administration APIs:</p>
<pre><code>^/_synapse/admin/v1/purge_media_cache$ <pre><code>^/_synapse/admin/v1/purge_media_cache$