MirrorHub/synapse
0
0
Fork 1
mirror of https://mau.dev/maunium/synapse.git synced 2024-06-01 02:08:56 +02:00
Code Issues Projects Releases Wiki Activity

Reword

Browse source
This commit is contained in:
Brendan Abolivier 2020-01-07 14:54:32 +00:00
parent 3a86477162
commit 391fb47791
No known key found for this signature in database
GPG key ID: 1E015C145F1916CD
2 changed files with 6 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
docs/sample_config.yaml
View file

@ -387,9 +387,9 @@ retention:
#
# The rationale for this per-job configuration is that some rooms might have a
# retention policy with a low 'max_lifetime', where history needs to be purged
# of outdated messages on a more frequent basis (e.g. every 12h), but not want
# that purge to be performed by a job that's iterating over every room it knows,
# which could be heavy on the server.
# of outdated messages on a more frequent basis than for the rest of the rooms
# (e.g. every 12h), but not want that purge to be performed by a job that's
# iterating over every room it knows, which could be heavy on the server.
#
#purge_jobs:
# - shortest_max_lifetime: 1d

6
synapse/config/server.py
View file

@ -948,9 +948,9 @@ class ServerConfig(Config):
#
# The rationale for this per-job configuration is that some rooms might have a
# retention policy with a low 'max_lifetime', where history needs to be purged
# of outdated messages on a more frequent basis (e.g. every 12h), but not want
# that purge to be performed by a job that's iterating over every room it knows,
# which could be heavy on the server.
# of outdated messages on a more frequent basis than for the rest of the rooms
# (e.g. every 12h), but not want that purge to be performed by a job that's
# iterating over every room it knows, which could be heavy on the server.
#
#purge_jobs:
# - shortest_max_lifetime: 1d