tileradotorg/synapse
1
0
Fork 0
forked from MirrorHub/synapse
Code Pull requests Activity

Sample config

Browse source
This commit is contained in:
Brendan Abolivier 2019-05-31 09:56:57 +01:00
parent 0c2362861e
commit 6bfc5ad3a1
1 changed files with 3 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
docs/sample_config.yaml
View file

@ -753,20 +753,15 @@ uploads_path: "DATADIR/uploads"
# This means that, if a validity period is set, and Synapse is restarted (it will
# then derive an expiration date from the current validity period), and some time
# after that the validity period changes and Synapse is restarted, the users'
# expiration dates won't be updated unless their account is manually renewed.
#
# If set, the ``startup_job_max_delta`` optional setting will make the startup job
# described above set a random expiration date between t + period and
# t + period + startup_job_max_delta, t being the date and time at which the job
# sets the expiration date for a given user. This is useful for server admins that
# want to avoid Synapse sending a lot of renewal emails at once.
# expiration dates won't be updated unless their account is manually renewed. This
# date will be randomly selected within a range [now + period ; now + period + d],
# where d is equal to 10% of the validity period.
#
#account_validity:
# enabled: True
# period: 6w
# renew_at: 1w
# renew_email_subject: "Renew your %(app)s account"
# startup_job_max_delta: 2d
# The user must provide all of the below types of 3PID when registering.
#