Skip to content
GitLab
Projects
Groups
Snippets
/
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Sign in
Toggle navigation
Menu
Open sidebar
Arch Linux
infrastructure
Commits
6813aa63
Verified
Commit
6813aa63
authored
Aug 19, 2020
by
Jan Alexander Steffens (heftig)
Browse files
matrix: Update homeserver config from sample_config.yaml
parent
d3a62d25
Changes
2
Hide whitespace changes
Inline
Side-by-side
roles/matrix/files/log_config.yaml
View file @
6813aa63
...
...
@@ -13,32 +13,54 @@ formatters:
journal_fmt
:
format
:
'
%(name)s:
[%(request)s]
%(message)s'
filters
:
context
:
()
:
synapse.logging.context.LoggingContextFilter
request
:
"
"
handlers
:
# Default to buffering writes to log file for efficiency. This means that
# will be a delay for INFO/DEBUG logs to get written, but WARNING/ERROR
# logs will still be flushed immediately.
buffer
:
class
:
logging.handlers.MemoryHandler
target
:
journal
# The capacity is the number of log lines that are buffered before
# being written to disk. Increasing this will lead to better
# performance, at the expensive of it taking longer for log lines to
# be written to disk.
capacity
:
10
flushLevel
:
30
# Flush for WARNING logs as well
# A handler that writes logs to stderr. Unused by default, but can be used
# instead of "buffer" and "file" in the logger handlers.
console
:
class
:
logging.StreamHandler
formatter
:
precise
filters
:
[
context
]
journal
:
class
:
systemd.journal.JournalHandler
formatter
:
journal_fmt
filters
:
[
context
]
SYSLOG_IDENTIFIER
:
synapse
loggers
:
synapse
:
level
:
INFO
synapse.storage.SQL
:
# beware: increasing this to DEBUG will make synapse log sensitive
# information such as access tokens.
level
:
INFO
twisted
:
# We send the twisted logging directly to the file handler,
# to work around https://github.com/matrix-org/synapse/issues/3471
# when using "buffer" logger. Use "console" to log to stderr instead.
handlers
:
[
journal
]
propagate
:
false
root
:
level
:
INFO
handlers
:
[
journal
]
# Write logs to the `buffer` handler, which will buffer them together in memory,
# then write them to a file.
#
# Replace "buffer" with "console" to log to stderr instead. (Note that you'll
# also need to update the configuation for the `twisted` logger above, in
# this case.)
#
handlers
:
[
buffer
]
disable_existing_loggers
:
false
roles/matrix/templates/homeserver.yaml.j2
View file @
6813aa63
# vim:ft=yaml sw=2 et:
# Configuration options that take a time period can be set using a number
# followed by a letter. Letters have the following meanings:
# s = second
# m = minute
# h = hour
# d = day
# w = week
# y = year
# For example, setting redaction_retention_period: 5m would remove redacted
# messages from the database after 5 minutes, rather than 5 months.
################################################################################
# Configuration file for Synapse.
...
...
@@ -311,6 +322,10 @@ limit_remote_rooms:
#
#complexity_error: "This room is too complex."
# allow server admins to join complex rooms. Default is false.
#
#admins_can_join: true
# Whether to require a user to be in the room to add an alias to it.
# Defaults to 'true'.
#
...
...
@@ -733,6 +748,10 @@ worker_log_config: "/etc/synapse/log_config.yaml"
# - one for ratelimiting redactions by room admins. If this is not explicitly
# set then it uses the same ratelimiting as per rc_message. This is useful
# to allow room admins to deal with abuse quickly.
# - two for ratelimiting number of rooms a user can join, "local" for when
# users are joining rooms the server is already in (this is cheap) vs
# "remote" for when users are trying to join rooms not on the server (which
# can be more expensive)
#
# The defaults are as shown below.
#
...
...
@@ -758,6 +777,14 @@ worker_log_config: "/etc/synapse/log_config.yaml"
#rc_admin_redaction:
# per_second: 1
# burst_count: 50
#
#rc_joins:
# local:
# per_second: 0.1
# burst_count: 3
# remote:
# per_second: 0.01
# burst_count: 3
# Ratelimiting settings for incoming federation
...
...
@@ -1147,24 +1174,6 @@ registration_shared_secret: "{{ vault_matrix_secrets[matrix_server_name].registr
#
default_identity_server
:
https://matrix.org
# The list of identity servers trusted to verify third party
# identifiers by this server.
#
# Also defines the ID server which will be called when an account is
# deactivated (one will be picked arbitrarily).
#
# Note: This option is deprecated. Since v0.99.4, Synapse has tracked which identity
# server a 3PID has been bound to. For 3PIDs bound before then, Synapse runs a
# background migration script, informing itself that the identity server all of its
# 3PIDs have been bound to is likely one of the below.
#
# As of Synapse v1.4.0, all other functionality of this option has been deprecated, and
# it is now solely used for the purposes of the background migration script, and can be
# removed once it has run.
#trusted_third_party_id_servers:
# - matrix.org
# - vector.im
# Handle threepid (email/phone etc) registration and password resets through a set of
# *trusted* identity servers. Note that this allows the configured identity server to
# reset passwords for accounts!
...
...
@@ -1569,6 +1578,17 @@ saml2_config:
#
#grandfathered_mxid_source_attribute: upn
# It is possible to configure Synapse to only allow logins if SAML attributes
# match particular values. The requirements can be listed under
# `attribute_requirements` as shown below. All of the listed attributes must
# match for the login to be permitted.
#
#attribute_requirements:
# - attribute: userGroup
# value: "staff"
# - attribute: department
# value: "sales"
# Directory in which Synapse will try to find the template files below.
# If not set, default templates from within the Synapse package will be used.
#
...
...
Write
Preview
Supports
Markdown
0%
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!
Cancel
Please
register
or
sign in
to comment