mirror of
https://git.envs.net/envs/matrix-conf.git
synced 2024-10-01 07:35:35 -04:00
update homeserver.yaml
This commit is contained in:
creme
parent
7e7439c22b
commit
859453de3e
@ -64,12 +64,29 @@ modules:
|
||||
- "!WuBtumawCeOGEieRrp:matrix.org"
|
||||
# matrix-tos-bl
|
||||
- "!tUPwPPmVTaiKXMiijj:matrix.org"
|
||||
# Public Servers Shared Banlist
|
||||
- "!RRGtWzzVKUJmDVRNnZ:aria-net.org"
|
||||
# tchncs-ban-list
|
||||
- "!hTMIYoLoENZQwslaHP:tchncs.de"
|
||||
# asragr-ban-list
|
||||
- "!YImXsibeOfGBYVaElT:asra.gr"
|
||||
# banlist-spam
|
||||
- "!eVqHGneqdbqBDmQwXs:systemtest.tk"
|
||||
#message_max_length:
|
||||
# Limit the characters in a message (event body) that a client can send in an event on this server.
|
||||
# By default there is no limit (beyond the the limit the spec enforces on event size).
|
||||
# Uncomment if you want messages to be limited to 510 characters.
|
||||
#threshold: 510
|
||||
# Limit messages only in certain rooms rooms.
|
||||
# By default all rooms will enforce the limit.
|
||||
# Uncomment if you want messages to only be subject to character limits in certain rooms.
|
||||
#rooms:
|
||||
# - "!vMvyOCeCxHsggkmALd:localhost:9999"
|
||||
# Also hide messages from remote servers that are over the `message_limit`.
|
||||
# By default only events from this server will be limited.
|
||||
# WARNING: Remote users on other servers will still be able to messages over the limit.
|
||||
# Uncomment to enforce the `message_limit` on events from remote servers.
|
||||
#remote_servers: true
|
||||
|
||||
|
||||
## Server ##
|
||||
@ -450,6 +467,11 @@ admin_contact: 'mailto:hostmaster@envs.net'
|
||||
# sign up in a short space of time never to return after their initial
|
||||
# session.
|
||||
#
|
||||
# The option `mau_appservice_trial_days` is similar to `mau_trial_days`, but
|
||||
# applies a different trial number if the user was registered by an appservice.
|
||||
# A value of 0 means no trial days are applied. Appservices not listed in this
|
||||
# dictionary use the value of `mau_trial_days` instead.
|
||||
#
|
||||
# 'mau_limit_alerting' is a means of limiting client side alerting
|
||||
# should the mau limit be reached. This is useful for small instances
|
||||
# where the admin has 5 mau seats (say) for 5 specific people and no
|
||||
@ -460,6 +482,8 @@ admin_contact: 'mailto:hostmaster@envs.net'
|
||||
#max_mau_value: 50
|
||||
#mau_trial_days: 2
|
||||
#mau_limit_alerting: false
|
||||
#mau_appservice_trial_days:
|
||||
# "appservice-id": 1
|
||||
|
||||
# If enabled, the metrics for the number of monthly active users will
|
||||
# be populated, however no one will be limited. If limit_usage_by_mau
|
||||
@ -761,11 +785,11 @@ retention:
|
||||
#
|
||||
#allow_profile_lookup_over_federation: false
|
||||
|
||||
# Uncomment to disable device display name lookup over federation. By default, the
|
||||
# Federation API allows other homeservers to obtain device display names of any user
|
||||
# on this homeserver. Defaults to 'true'.
|
||||
# Uncomment to allow device display name lookup over federation. By default, the
|
||||
# Federation API prevents other homeservers from obtaining the display names of
|
||||
# user devices on this homeserver. Defaults to 'false'.
|
||||
#
|
||||
#allow_device_name_lookup_over_federation: false
|
||||
#allow_device_name_lookup_over_federation: true
|
||||
|
||||
|
||||
## Caching ##
|
||||
@ -2722,9 +2746,9 @@ opentracing:
|
||||
worker_app: synapse.app.homeserver
|
||||
#worker_name: synapse
|
||||
|
||||
notify_appservices: false
|
||||
#notify_appservices_from_worker: worker_name
|
||||
start_pushers: false
|
||||
#update_user_directory: false
|
||||
#update_user_directory_from_worker: worker_name
|
||||
|
||||
# Disables sending of outbound federation transactions on the main process.
|
||||
# Uncomment if using a federation sender worker.
|
||||
|
||||
@ -1,13 +0,0 @@
|
||||
worker_app: synapse.app.appservice
|
||||
worker_name: appservice
|
||||
|
||||
# The replication listener on the synapse to talk to.
|
||||
worker_replication_host: 127.0.0.1
|
||||
worker_replication_http_port: 9093
|
||||
|
||||
worker_log_config: /etc/matrix-synapse/workers/appservice_log_config.yaml
|
||||
|
||||
worker_listeners:
|
||||
- type: metrics
|
||||
bind_addresses: ['0.0.0.0']
|
||||
port: 9121
|
||||
@ -1,84 +0,0 @@
|
||||
# Log configuration for Synapse.
|
||||
#
|
||||
# This is a YAML file containing a standard Python logging configuration
|
||||
# dictionary. See [1] for details on the valid settings.
|
||||
#
|
||||
# Synapse also supports structured logging for machine readable logs which can
|
||||
# be ingested by ELK stacks. See [2] for details.
|
||||
#
|
||||
# [1]: https://docs.python.org/3.7/library/logging.config.html#configuration-dictionary-schema
|
||||
# [2]: https://matrix-org.github.io/synapse/latest/structured_logging.html
|
||||
|
||||
version: 1
|
||||
|
||||
formatters:
|
||||
precise:
|
||||
format: '%(asctime)s - %(name)s - %(lineno)d - %(levelname)s - %(request)s - %(message)s'
|
||||
|
||||
handlers:
|
||||
file:
|
||||
class: logging.handlers.TimedRotatingFileHandler
|
||||
formatter: precise
|
||||
filename: /var/log/matrix-synapse/worker_appservice.log
|
||||
when: midnight
|
||||
backupCount: 2 # Does not include the current log file.
|
||||
encoding: utf8
|
||||
|
||||
# Default to buffering writes to log file for efficiency.
|
||||
# WARNING/ERROR logs will still be flushed immediately, but there will be a
|
||||
# delay (of up to `period` seconds, or until the buffer is full with
|
||||
# `capacity` messages) before INFO/DEBUG logs get written.
|
||||
buffer:
|
||||
class: synapse.logging.handlers.PeriodicallyFlushingMemoryHandler
|
||||
target: file
|
||||
|
||||
# The capacity is the maximum 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.
|
||||
# This parameter is required.
|
||||
capacity: 10
|
||||
|
||||
# Logs with a level at or above the flush level will cause the buffer to
|
||||
# be flushed immediately.
|
||||
# Default value: 40 (ERROR)
|
||||
# Other values: 50 (CRITICAL), 30 (WARNING), 20 (INFO), 10 (DEBUG)
|
||||
flushLevel: 30 # Flush immediately for WARNING logs and higher
|
||||
|
||||
# The period of time, in seconds, between forced flushes.
|
||||
# Messages will not be delayed for longer than this time.
|
||||
# Default value: 5 seconds
|
||||
period: 5
|
||||
|
||||
# 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
|
||||
|
||||
loggers:
|
||||
synapse.storage.SQL:
|
||||
# beware: increasing this to DEBUG will make synapse log sensitive
|
||||
# information such as access tokens.
|
||||
level: WARN
|
||||
|
||||
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: [file]
|
||||
propagate: false
|
||||
|
||||
root:
|
||||
level: WARN
|
||||
|
||||
# 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 configuration for the `twisted` logger above, in
|
||||
# this case.)
|
||||
#
|
||||
handlers: [buffer]
|
||||
|
||||
disable_existing_loggers: false
|
||||
Loading…
Reference in New Issue
Block a user