Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
synapse
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Monitor
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Maunium
synapse
Commits
391fb477
Unverified
Commit
391fb477
authored
5 years ago
by
Brendan Abolivier
Browse files
Options
Downloads
Patches
Plain Diff
Reword
parent
3a864771
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
docs/sample_config.yaml
+3
-3
3 additions, 3 deletions
docs/sample_config.yaml
synapse/config/server.py
+3
-3
3 additions, 3 deletions
synapse/config/server.py
with
6 additions
and
6 deletions
docs/sample_config.yaml
+
3
−
3
View file @
391fb477
...
...
@@ -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
...
...
This diff is collapsed.
Click to expand it.
synapse/config/server.py
+
3
−
3
View file @
391fb477
...
...
@@ -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
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment