mirrors/synapse
mirrors/synapse
1
0
Fork 0
mirror of https://github.com/element-hq/synapse.git synced 2025-03-31 03:45:13 +00:00
Code Activity

deploy: e26673fe97

Browse source
This commit is contained in:
anoadragon453 2024-04-30 13:44:06 +00:00
parent d0ba599fdb
commit 64be1a1491
6 changed files with 14 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
latest/development/contributing_guide.html
View file

@ -214,6 +214,7 @@ poetry install --extras all
</code></pre> </code></pre>
<p>This will install the runtime and developer dependencies for the project. Be sure to check <p>This will install the runtime and developer dependencies for the project. Be sure to check
that the <code>poetry install</code> step completed cleanly.</p> that the <code>poetry install</code> step completed cleanly.</p>
<p>For OSX users, be sure to set <code>PKG_CONFIG_PATH</code> to support <code>icu4c</code>. Run <code>brew info icu4c</code> for more details.</p>
<h2 id="running-synapse-via-poetry"><a class="header" href="#running-synapse-via-poetry">Running Synapse via poetry</a></h2> <h2 id="running-synapse-via-poetry"><a class="header" href="#running-synapse-via-poetry">Running Synapse via poetry</a></h2>
<p>To start a local instance of Synapse in the locked poetry environment, create a config file:</p> <p>To start a local instance of Synapse in the locked poetry environment, create a config file:</p>
<pre><code class="language-sh">cp docs/sample_config.yaml homeserver.yaml <pre><code class="language-sh">cp docs/sample_config.yaml homeserver.yaml

6
latest/message_retention_policies.html
View file

@ -167,8 +167,10 @@ follow the semantics described in
and allow server and room admins to configure how long messages should and allow server and room admins to configure how long messages should
be kept in a homeserver's database before being purged from it. be kept in a homeserver's database before being purged from it.
<strong>Please note that, as this feature isn't part of the Matrix <strong>Please note that, as this feature isn't part of the Matrix
specification yet, this implementation is to be considered as specification yet, the use of <code>m.room.retention</code> events for per-room
experimental.</strong></p> retention policies is to be considered as experimental. However, the use
of a default message retention policy is considered a stable feature
in Synapse.</strong></p>
<p>A message retention policy is mainly defined by its <code>max_lifetime</code> <p>A message retention policy is mainly defined by its <code>max_lifetime</code>
parameter, which defines how long a message can be kept around after parameter, which defines how long a message can be kept around after
it was sent to the room. If a room doesn't have a message retention it was sent to the room. If a room doesn't have a message retention

9
latest/print.html
View file

@ -1842,7 +1842,7 @@ v1.61.0.</p>
<tr><td>v1.85.0 – v1.91.2</td><td>v1.83.0</td></tr> <tr><td>v1.85.0 – v1.91.2</td><td>v1.83.0</td></tr>
<tr><td>v1.92.0 – v1.97.0</td><td>v1.90.0</td></tr> <tr><td>v1.92.0 – v1.97.0</td><td>v1.90.0</td></tr>
<tr><td>v1.98.0 – v1.105.0</td><td>v1.96.0</td></tr> <tr><td>v1.98.0 – v1.105.0</td><td>v1.96.0</td></tr>
<tr><td>v1.105.1 – v1.105.1</td><td>v1.100.0</td></tr> <tr><td>v1.105.1 – v1.106.0</td><td>v1.100.0</td></tr>
</tbody></table> </tbody></table>
<h2 id="upgrading-from-a-very-old-version"><a class="header" href="#upgrading-from-a-very-old-version">Upgrading from a very old version</a></h2> <h2 id="upgrading-from-a-very-old-version"><a class="header" href="#upgrading-from-a-very-old-version">Upgrading from a very old version</a></h2>
<p>You need to read all of the upgrade notes for each version between your current <p>You need to read all of the upgrade notes for each version between your current
@ -9820,8 +9820,10 @@ follow the semantics described in
and allow server and room admins to configure how long messages should and allow server and room admins to configure how long messages should
be kept in a homeserver's database before being purged from it. be kept in a homeserver's database before being purged from it.
<strong>Please note that, as this feature isn't part of the Matrix <strong>Please note that, as this feature isn't part of the Matrix
specification yet, this implementation is to be considered as specification yet, the use of <code>m.room.retention</code> events for per-room
experimental.</strong></p> retention policies is to be considered as experimental. However, the use
of a default message retention policy is considered a stable feature
in Synapse.</strong></p>
<p>A message retention policy is mainly defined by its <code>max_lifetime</code> <p>A message retention policy is mainly defined by its <code>max_lifetime</code>
parameter, which defines how long a message can be kept around after parameter, which defines how long a message can be kept around after
it was sent to the room. If a room doesn't have a message retention it was sent to the room. If a room doesn't have a message retention
@ -16569,6 +16571,7 @@ poetry install --extras all
</code></pre> </code></pre>
<p>This will install the runtime and developer dependencies for the project. Be sure to check <p>This will install the runtime and developer dependencies for the project. Be sure to check
that the <code>poetry install</code> step completed cleanly.</p> that the <code>poetry install</code> step completed cleanly.</p>
<p>For OSX users, be sure to set <code>PKG_CONFIG_PATH</code> to support <code>icu4c</code>. Run <code>brew info icu4c</code> for more details.</p>
<h2 id="running-synapse-via-poetry"><a class="header" href="#running-synapse-via-poetry">Running Synapse via poetry</a></h2> <h2 id="running-synapse-via-poetry"><a class="header" href="#running-synapse-via-poetry">Running Synapse via poetry</a></h2>
<p>To start a local instance of Synapse in the locked poetry environment, create a config file:</p> <p>To start a local instance of Synapse in the locked poetry environment, create a config file:</p>
<pre><code class="language-sh">cp docs/sample_config.yaml homeserver.yaml <pre><code class="language-sh">cp docs/sample_config.yaml homeserver.yaml

2
latest/searchindex.js
View file

File diff suppressed because one or more lines are too long

2
latest/searchindex.json
View file

File diff suppressed because one or more lines are too long

2
latest/upgrade.html
View file

@ -267,7 +267,7 @@ v1.61.0.</p>
<tr><td>v1.85.0 – v1.91.2</td><td>v1.83.0</td></tr> <tr><td>v1.85.0 – v1.91.2</td><td>v1.83.0</td></tr>
<tr><td>v1.92.0 – v1.97.0</td><td>v1.90.0</td></tr> <tr><td>v1.92.0 – v1.97.0</td><td>v1.90.0</td></tr>
<tr><td>v1.98.0 – v1.105.0</td><td>v1.96.0</td></tr> <tr><td>v1.98.0 – v1.105.0</td><td>v1.96.0</td></tr>
<tr><td>v1.105.1 – v1.105.1</td><td>v1.100.0</td></tr> <tr><td>v1.105.1 – v1.106.0</td><td>v1.100.0</td></tr>
</tbody></table> </tbody></table>
<h2 id="upgrading-from-a-very-old-version"><a class="header" href="#upgrading-from-a-very-old-version">Upgrading from a very old version</a></h2> <h2 id="upgrading-from-a-very-old-version"><a class="header" href="#upgrading-from-a-very-old-version">Upgrading from a very old version</a></h2>
<p>You need to read all of the upgrade notes for each version between your current <p>You need to read all of the upgrade notes for each version between your current