summary refs log tree commit diff
path: root/latest/usage
diff options
context:
space:
mode:
authorsquahtx <squahtx@users.noreply.github.com>2022-04-05 14:15:14 +0000
committersquahtx <squahtx@users.noreply.github.com>2022-04-05 14:15:14 +0000
commit520cf4ab2ca7474a6cce67531b305ed0fee20548 (patch)
treeb2fd9a03fc8240209c8413c72688c530b4e0c2e7 /latest/usage
parentdeploy: 708d88b1a22d422c294c4d06f2896a24f2a0251d (diff)
downloadsynapse-520cf4ab2ca7474a6cce67531b305ed0fee20548.tar.xz
deploy: ac80bfba4252c3bb8138cc3711271be63182eed8
Diffstat (limited to 'latest/usage')
-rw-r--r--latest/usage/configuration/homeserver_sample_config.html16
1 files changed, 15 insertions, 1 deletions
diff --git a/latest/usage/configuration/homeserver_sample_config.html b/latest/usage/configuration/homeserver_sample_config.html
index f932eb2955..153336aa7f 100644
--- a/latest/usage/configuration/homeserver_sample_config.html
+++ b/latest/usage/configuration/homeserver_sample_config.html
@@ -975,6 +975,12 @@ caches:
 # 'txn_limit' gives the maximum number of transactions to run per connection
 # before reconnecting. Defaults to 0, which means no limit.
 #
+# 'allow_unsafe_locale' is an option specific to Postgres. Under the default behavior, Synapse will refuse to
+# start if the postgres db is set to a non-C locale. You can override this behavior (which is *not* recommended)
+# by setting 'allow_unsafe_locale' to true. Note that doing so may corrupt your database. You can find more information
+# here: https://matrix-org.github.io/synapse/latest/postgres.html#fixing-incorrect-collate-or-ctype and here:
+# https://wiki.postgresql.org/wiki/Locale_data_changes
+#
 # 'args' gives options which are passed through to the database engine,
 # except for options starting 'cp_', which are used to configure the Twisted
 # connection pool. For a reference to valid arguments, see:
@@ -1404,10 +1410,18 @@ oembed:
 # Registration can be rate-limited using the parameters in the &quot;Ratelimiting&quot;
 # section of this file.
 
-# Enable registration for new users.
+# Enable registration for new users. Defaults to 'false'. It is highly recommended that if you enable registration,
+# you use either captcha, email, or token-based verification to verify that new users are not bots. In order to enable registration
+# without any verification, you must also set `enable_registration_without_verification`, found below.
 #
 #enable_registration: false
 
+# Enable registration without email or captcha verification. Note: this option is *not* recommended,
+# as registration without verification is a known vector for spam and abuse. Defaults to false. Has no effect
+# unless `enable_registration` is also enabled.
+#
+#enable_registration_without_verification: true
+
 # Time that a user's session remains valid for, after they log in.
 #
 # Note that this is not currently compatible with guest logins.