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
3675fb9b
Unverified
Commit
3675fb9b
authored
5 years ago
by
Brendan Abolivier
Browse files
Options
Downloads
Patches
Plain Diff
Fix reference
parent
7ba98a28
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
docs/message_retention_policies.md
+1
-1
1 addition, 1 deletion
docs/message_retention_policies.md
with
1 addition
and
1 deletion
docs/message_retention_policies.md
+
1
−
1
View file @
3675fb9b
...
@@ -83,7 +83,7 @@ expired events from the database. They are only run if support for
...
@@ -83,7 +83,7 @@ expired events from the database. They are only run if support for
message retention policies is enabled in the server's configuration. If
message retention policies is enabled in the server's configuration. If
no configuration for purge jobs is configured by the server admin,
no configuration for purge jobs is configured by the server admin,
Synapse will use a default configuration, which is described in the
Synapse will use a default configuration, which is described in the
[
sample configuration file
](
https://github.com/matrix-org/synapse/blob/
v1.7.3
/docs/sample_config.yaml#L332-L393
)
.
[
sample configuration file
](
https://github.com/matrix-org/synapse/blob/
master
/docs/sample_config.yaml#L332-L393
)
.
Some server admins might want a finer control on when events are removed
Some server admins might want a finer control on when events are removed
depending on an event's room's policy. This can be done by setting the
depending on an event's room's policy. This can be done by setting the
...
...
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