Raw YAML - Releases: latest, v26.04, v26.03, v26.02, v25.11, v25.10
1# Network-specific config options
2network:
3 # Displayname template for Slack users. Available variables:
4 # .Name - The username of the user
5 # .Team.Name - The name of the team the channel is in
6 # .Team.Domain - The Slack subdomain of the team the channel is in
7 # .ID - The internal ID of the user
8 # .IsBot - Whether the user is a bot
9 # .Profile.DisplayName - The username or real name of the user (depending on settings)
10 # Variables only available for users (not bots):
11 # .TeamID - The internal ID of the workspace the user is in
12 # .TZ - The timezone region of the user (e.g. Europe/London)
13 # .TZLabel - The label of the timezone of the user (e.g. Greenwich Mean Time)
14 # .TZOffset - The UTC offset of the timezone of the user (e.g. 0)
15 # .Profile.RealName - The real name of the user
16 # .Profile.FirstName - The first name of the user
17 # .Profile.LastName - The last name of the user
18 # .Profile.Title - The job title of the user
19 # .Profile.Pronouns - The pronouns of the user
20 # .Profile.Email - The email address of the user
21 # .Profile.Phone - The formatted phone number of the user
22 displayname_template: '{{or .Profile.DisplayName .Profile.RealName .Name}}{{if .IsBot}} (bot){{end}}'
23 # Channel name template for Slack channels (all types). Available variables:
24 # .Name - The name of the channel
25 # .Team.Name - The name of the team the channel is in
26 # .Team.Domain - The Slack subdomain of the team the channel is in
27 # .ID - The internal ID of the channel
28 # .IsNoteToSelf - Whether the channel is a DM with yourself
29 # .IsGeneral - Whether the channel is the #general channel
30 # .IsChannel - Whether the channel is a channel (rather than a DM)
31 # .IsPrivate - Whether the channel is private
32 # .IsIM - Whether the channel is a one-to-one DM
33 # .IsMpIM - Whether the channel is a group DM
34 # .IsShared - Whether the channel is shared with another workspace.
35 # .IsExtShared - Whether the channel is shared with an external organization.
36 # .IsOrgShared - Whether the channel is shared with an organization in the same enterprise grid.
37 channel_name_template: '{{if and .IsChannel (not .IsPrivate)}}#{{end}}{{.Name}}{{if .IsNoteToSelf}} (you){{end}}'
38 # Displayname template for Slack workspaces. Available variables:
39 # .Name - The name of the team
40 # .Domain - The Slack subdomain of the team
41 # .ID - The internal ID of the team
42 team_name_template: "{{ .Name }}"
43
44 # Should incoming custom emoji reactions be bridged as mxc:// URIs?
45 # If set to false, custom emoji reactions will be bridged as the shortcode instead, and the image won't be available.
46 custom_emoji_reactions: true
47 # Should channels and group DMs have the workspace icon as the Matrix room avatar?
48 workspace_avatar_in_rooms: false
49 # Number of participants to sync in channels (doesn't affect group DMs)
50 participant_sync_count: 5
51 # Should channel participants only be synced when creating the room?
52 # If you want participants to always be accurately synced, set participant_sync_count to a high value and this to false.
53 participant_sync_only_on_create: true
54 # Should channel portals be muted by default?
55 mute_channels_by_default: false
56
57 # Options for backfilling messages from Slack.
58 backfill:
59 # Number of conversations to fetch from Slack when syncing workspace.
60 # This option applies even if message backfill is disabled below.
61 # If set to -1, all chats in the client.boot response will be bridged, and nothing will be fetched separately.
62 conversation_count: -1
63
64
65# Config options that affect the central bridge module.
66bridge:
67 # The prefix for commands. Only required in non-management rooms.
68 command_prefix: '!slack'
69 # Should the bridge create a space for each login containing the rooms that account is in?
70 personal_filtering_spaces: true
71 # Whether the bridge should set names and avatars explicitly for DM portals.
72 # This is only necessary when using clients that don't support MSC4171.
73 private_chat_portal_meta: true
74 # Should events be handled asynchronously within portal rooms?
75 # If true, events may end up being out of order, but slow events won't block other ones.
76 # This is not yet safe to use.
77 async_events: false
78 # Should every user have their own portals rather than sharing them?
79 # By default, users who are in the same group on the remote network will be
80 # in the same Matrix room bridged to that group. If this is set to true,
81 # every user will get their own Matrix room instead.
82 # SETTING THIS IS IRREVERSIBLE AND POTENTIALLY DESTRUCTIVE IF PORTALS ALREADY EXIST.
83 split_portals: false
84 # Should the bridge resend `m.bridge` events to all portals on startup?
85 resend_bridge_info: false
86 # Should `m.bridge` events be sent without a state key?
87 # By default, the bridge uses a unique key that won't conflict with other bridges.
88 no_bridge_info_state_key: false
89 # Should bridge connection status be sent to the management room as `m.notice` events?
90 # These contain the same data that can be posted to an external HTTP server using homeserver -> status_endpoint.
91 # Allowed values: none, errors, all
92 bridge_status_notices: errors
93 # How long after an unknown error should the bridge attempt a full reconnect?
94 # Must be at least 1 minute. The bridge will add an extra ±20% jitter to this value.
95 unknown_error_auto_reconnect: null
96
97 # Should leaving Matrix rooms be bridged as leaving groups on the remote network?
98 bridge_matrix_leave: false
99 # Should `m.notice` messages be bridged?
100 bridge_notices: false
101 # Should room tags only be synced when creating the portal? Tags mean things like favorite/pin and archive/low priority.
102 # Tags currently can't be synced back to the remote network, so a continuous sync means tagging from Matrix will be undone.
103 tag_only_on_create: true
104 # List of tags to allow bridging. If empty, no tags will be bridged.
105 only_bridge_tags: [m.favourite, m.lowpriority]
106 # Should room mute status only be synced when creating the portal?
107 # Like tags, mutes can't currently be synced back to the remote network.
108 mute_only_on_create: true
109 # Should the bridge check the db to ensure that incoming events haven't been handled before
110 deduplicate_matrix_messages: false
111 # Should cross-room reply metadata be bridged?
112 # Most Matrix clients don't support this and servers may reject such messages too.
113 cross_room_replies: false
114 # If a state event fails to bridge, should the bridge revert any state changes made by that event?
115 revert_failed_state_changes: false
116 # In portals with no relay set, should Matrix users be kicked if they're
117 # not logged into an account that's in the remote chat?
118 kick_matrix_users: true
119
120 # What should be done to portal rooms when a user logs out or is logged out?
121 # Permitted values:
122 # nothing - Do nothing, let the user stay in the portals
123 # kick - Remove the user from the portal rooms, but don't delete them
124 # unbridge - Remove all ghosts in the room and disassociate it from the remote chat
125 # delete - Remove all ghosts and users from the room (i.e. delete it)
126 cleanup_on_logout:
127 # Should cleanup on logout be enabled at all?
128 enabled: false
129 # Settings for manual logouts (explicitly initiated by the Matrix user)
130 manual:
131 # Action for private portals which will never be shared with other Matrix users.
132 private: nothing
133 # Action for portals with a relay user configured.
134 relayed: nothing
135 # Action for portals which may be shared, but don't currently have any other Matrix users.
136 shared_no_users: nothing
137 # Action for portals which have other logged-in Matrix users.
138 shared_has_users: nothing
139 # Settings for credentials being invalidated (initiated by the remote network, possibly through user action).
140 # Keys have the same meanings as in the manual section.
141 bad_credentials:
142 private: nothing
143 relayed: nothing
144 shared_no_users: nothing
145 shared_has_users: nothing
146
147 # Settings for relay mode
148 relay:
149 # Whether relay mode should be allowed. If allowed, the set-relay command can be used to turn any
150 # authenticated user into a relaybot for that chat.
151 enabled: false
152 # Should only admins be allowed to set themselves as relay users?
153 # If true, non-admins can only set users listed in default_relays as relays in a room.
154 admin_only: true
155 # List of user login IDs which anyone can set as a relay, as long as the relay user is in the room.
156 default_relays: []
157 # The formats to use when sending messages via the relaybot.
158 # Available variables:
159 # .Sender.UserID - The Matrix user ID of the sender.
160 # .Sender.Displayname - The display name of the sender (if set).
161 # .Sender.RequiresDisambiguation - Whether the sender's name may be confused with the name of another user in the room.
162 # .Sender.DisambiguatedName - The disambiguated name of the sender. This will be the displayname if set,
163 # plus the user ID in parentheses if the displayname is not unique.
164 # If the displayname is not set, this is just the user ID.
165 # .Message - The `formatted_body` field of the message.
166 # .Caption - The `formatted_body` field of the message, if it's a caption. Otherwise an empty string.
167 # .FileName - The name of the file being sent.
168 message_formats:
169 m.text: "<b>{{ .Sender.DisambiguatedName }}</b>: {{ .Message }}"
170 m.notice: "<b>{{ .Sender.DisambiguatedName }}</b>: {{ .Message }}"
171 m.emote: "* <b>{{ .Sender.DisambiguatedName }}</b> {{ .Message }}"
172 m.file: "<b>{{ .Sender.DisambiguatedName }}</b> sent a file{{ if .Caption }}: {{ .Caption }}{{ end }}"
173 m.image: "<b>{{ .Sender.DisambiguatedName }}</b> sent an image{{ if .Caption }}: {{ .Caption }}{{ end }}"
174 m.audio: "<b>{{ .Sender.DisambiguatedName }}</b> sent an audio file{{ if .Caption }}: {{ .Caption }}{{ end }}"
175 m.video: "<b>{{ .Sender.DisambiguatedName }}</b> sent a video{{ if .Caption }}: {{ .Caption }}{{ end }}"
176 m.location: "<b>{{ .Sender.DisambiguatedName }}</b> sent a location{{ if .Caption }}: {{ .Caption }}{{ end }}"
177 # For networks that support per-message displaynames (i.e. Slack and Discord), the template for those names.
178 # This has all the Sender variables available under message_formats (but without the .Sender prefix).
179 # Note that you need to manually remove the displayname from message_formats above.
180 displayname_format: "{{ .DisambiguatedName }}"
181
182 # Permissions for using the bridge.
183 # Permitted values:
184 # relay - Talk through the relaybot (if enabled), no access otherwise
185 # commands - Access to use commands in the bridge, but not login.
186 # user - Access to use the bridge with puppeting.
187 # admin - Full access, user level with some additional administration tools.
188 # Permitted keys:
189 # * - All Matrix users
190 # domain - All users on that homeserver
191 # mxid - Specific user
192 permissions:
193 "*": relay
194 "example.com": user
195 "@admin:example.com": admin
196
197# Config for the bridge's database.
198database:
199 # The database type. "sqlite3-fk-wal" and "postgres" are supported.
200 type: postgres
201 # The database URI.
202 # SQLite: A raw file path is supported, but `file:<path>?_txlock=immediate` is recommended.
203 # https://github.com/mattn/go-sqlite3#connection-string
204 # Postgres: Connection string. For example, postgres://user:password@host/database?sslmode=disable
205 # To connect via Unix socket, use something like postgres:///dbname?host=/var/run/postgresql
206 uri: postgres://user:password@host/database?sslmode=disable
207 # Maximum number of connections.
208 max_open_conns: 5
209 max_idle_conns: 1
210 # Maximum connection idle time and lifetime before they're closed. Disabled if null.
211 # Parsed with https://pkg.go.dev/time#ParseDuration
212 max_conn_idle_time: null
213 max_conn_lifetime: null
214
215# Homeserver details.
216homeserver:
217 # The address that this appservice can use to connect to the homeserver.
218 # Local addresses without HTTPS are generally recommended when the bridge is running on the same machine,
219 # but https also works if they run on different machines.
220 address: http://example.localhost:8008
221 # The domain of the homeserver (also known as server_name, used for MXIDs, etc).
222 domain: example.com
223
224 # What software is the homeserver running?
225 # Standard Matrix homeservers like Synapse, Dendrite and Conduit should just use "standard" here.
226 software: standard
227 # The URL to push real-time bridge status to.
228 # If set, the bridge will make POST requests to this URL whenever a user's remote network connection state changes.
229 # The bridge will use the appservice as_token to authorize requests.
230 status_endpoint:
231 # Endpoint for reporting per-message status.
232 # If set, the bridge will make POST requests to this URL when processing a message from Matrix.
233 # It will make one request when receiving the message (step BRIDGE), one after decrypting if applicable
234 # (step DECRYPTED) and one after sending to the remote network (step REMOTE). Errors will also be reported.
235 # The bridge will use the appservice as_token to authorize requests.
236 message_send_checkpoint_endpoint:
237 # Does the homeserver support https://github.com/matrix-org/matrix-spec-proposals/pull/2246?
238 async_media: false
239
240 # Should the bridge use a websocket for connecting to the homeserver?
241 # The server side is currently not documented anywhere and is only implemented by mautrix-wsproxy,
242 # mautrix-asmux (deprecated), and hungryserv (proprietary).
243 websocket: false
244 # How often should the websocket be pinged? Pinging will be disabled if this is zero.
245 ping_interval_seconds: 0
246
247# Application service host/registration related details.
248# Changing these values requires regeneration of the registration (except when noted otherwise)
249appservice:
250 # The address that the homeserver can use to connect to this appservice.
251 # Like the homeserver address, a local non-https address is recommended when the bridge is on the same machine.
252 # If the bridge is elsewhere, you must secure the connection yourself (e.g. with https or wireguard)
253 # If you want to use https, you need to use a reverse proxy. The bridge does not have TLS support built in.
254 address: http://localhost:29335
255 # A public address that external services can use to reach this appservice.
256 # This is only needed for things like public media. A reverse proxy is generally necessary when using this field.
257 # This value doesn't affect the registration file.
258 public_address: https://bridge.example.com
259
260 # The hostname and port where this appservice should listen.
261 # For Docker, you generally have to change the hostname to 0.0.0.0.
262 hostname: 127.0.0.1
263 port: 29335
264
265 # The unique ID of this appservice.
266 id: slack
267 # Appservice bot details.
268 bot:
269 # Username of the appservice bot.
270 username: slackbot
271 # Display name and avatar for bot. Set to "remove" to remove display name/avatar, leave empty
272 # to leave display name/avatar as-is.
273 displayname: Slack bridge bot
274 avatar: mxc://maunium.net/pVtzLmChZejGxLqmXtQjFxem
275
276 # Whether to receive ephemeral events via appservice transactions.
277 ephemeral_events: true
278 # Should incoming events be handled asynchronously?
279 # This may be necessary for large public instances with lots of messages going through.
280 # However, messages will not be guaranteed to be bridged in the same order they were sent in.
281 # This value doesn't affect the registration file.
282 async_transactions: false
283
284 # Authentication tokens for AS <-> HS communication. Autogenerated; do not modify.
285 as_token: "This value is generated when generating the registration"
286 hs_token: "This value is generated when generating the registration"
287
288 # Localpart template of MXIDs for remote users.
289 # {{.}} is replaced with the internal ID of the user.
290 username_template: slack_{{.}}
291
292# Config options that affect the Matrix connector of the bridge.
293matrix:
294 # Whether the bridge should send the message status as a custom com.beeper.message_send_status event.
295 message_status_events: false
296 # Whether the bridge should send a read receipt after successfully bridging a message.
297 delivery_receipts: false
298 # Whether the bridge should send error notices via m.notice events when a message fails to bridge.
299 message_error_notices: true
300 # Whether the bridge should update the m.direct account data event when double puppeting is enabled.
301 sync_direct_chat_list: true
302 # Whether created rooms should have federation enabled. If false, created portal rooms
303 # will never be federated. Changing this option requires recreating rooms.
304 federate_rooms: true
305 # The threshold as bytes after which the bridge should roundtrip uploads via the disk
306 # rather than keeping the whole file in memory.
307 upload_file_threshold: 5242880
308
309# Segment-compatible analytics endpoint for tracking some events, like provisioning API login and encryption errors.
310analytics:
311 # API key to send with tracking requests. Tracking is disabled if this is null.
312 token: null
313 # Address to send tracking requests to.
314 url: https://api.segment.io/v1/track
315 # Optional user ID for tracking events. If null, defaults to using Matrix user ID.
316 user_id: null
317
318# Settings for provisioning API
319provisioning:
320 # Shared secret for authentication. If set to "generate" or null, a random secret will be generated,
321 # or if set to "disable", the provisioning API will be disabled. Must be at least 16 characters.
322 shared_secret: generate
323 # Whether to allow provisioning API requests to be authed using Matrix access tokens.
324 # This follows the same rules as double puppeting to determine which server to contact to check the token,
325 # which means that by default, it only works for users on the same server as the bridge.
326 allow_matrix_auth: true
327 # Enable debug API at /debug with provisioning authentication.
328 debug_endpoints: false
329 # Enable session transfers between bridges. Note that this only validates Matrix or shared secret
330 # auth before passing live network client credentials down in the response.
331 enable_session_transfers: false
332
333# Some networks require publicly accessible media download links (e.g. for user avatars when using Discord webhooks).
334# These settings control whether the bridge will provide such public media access.
335public_media:
336 # Should public media be enabled at all?
337 # The public_address field under the appservice section MUST be set when enabling public media.
338 enabled: false
339 # A key for signing public media URLs.
340 # If set to "generate", a random key will be generated.
341 signing_key: generate
342 # Number of seconds that public media URLs are valid for.
343 # If set to 0, URLs will never expire.
344 expiry: 0
345 # Length of hash to use for public media URLs. Must be between 0 and 32.
346 hash_length: 32
347 # The path prefix for generated URLs. Note that this will NOT change the path where media is actually served.
348 # If you change this, you must configure your reverse proxy to rewrite the path accordingly.
349 path_prefix: /_mautrix/publicmedia
350 # Should the bridge store media metadata in the database in order to support encrypted media and generate shorter URLs?
351 # If false, the generated URLs will just have the MXC URI and a HMAC signature.
352 # The hash_length field will be used to decide the length of the generated URL.
353 # This also allows invalidating URLs by deleting the database entry.
354 use_database: false
355
356# Settings for converting remote media to custom mxc:// URIs instead of reuploading.
357# More details can be found at https://docs.mau.fi/bridges/go/discord/direct-media.html
358direct_media:
359 # Should custom mxc:// URIs be used instead of reuploading media?
360 enabled: false
361 # The server name to use for the custom mxc:// URIs.
362 # This server name will effectively be a real Matrix server, it just won't implement anything other than media.
363 # You must either set up .well-known delegation from this domain to the bridge, or proxy the domain directly to the bridge.
364 server_name: discord-media.example.com
365 # Optionally a custom .well-known response. This defaults to `server_name:443`
366 well_known_response:
367 # Optionally specify a custom prefix for the media ID part of the MXC URI.
368 media_id_prefix:
369 # If the remote network supports media downloads over HTTP, then the bridge will use MSC3860/MSC3916
370 # media download redirects if the requester supports it. Optionally, you can force redirects
371 # and not allow proxying at all by setting this to false.
372 # This option does nothing if the remote network does not support media downloads over HTTP.
373 allow_proxy: true
374 # Matrix server signing key to make the federation tester pass, same format as synapse's .signing.key file.
375 # This key is also used to sign the mxc:// URIs to ensure only the bridge can generate them.
376 server_key: generate
377
378# Settings for backfilling messages.
379# Note that the exact way settings are applied depends on the network connector.
380# See https://docs.mau.fi/bridges/general/backfill.html for more details.
381backfill:
382 # Whether to do backfilling at all.
383 enabled: false
384 # Maximum number of messages to backfill in empty rooms.
385 max_initial_messages: 50
386 # Maximum number of missed messages to backfill after bridge restarts.
387 max_catchup_messages: 500
388 # If a backfilled chat is older than this number of hours,
389 # mark it as read even if it's unread on the remote network.
390 unread_hours_threshold: 720
391 # Settings for backfilling threads within other backfills.
392 threads:
393 # Maximum number of messages to backfill in a new thread.
394 max_initial_messages: 50
395 # Settings for the backwards backfill queue. This only applies when connecting to
396 # Beeper as standard Matrix servers don't support inserting messages into history.
397 queue:
398 # Should the backfill queue be enabled?
399 enabled: false
400 # Number of messages to backfill in one batch.
401 batch_size: 100
402 # Delay between batches in seconds.
403 batch_delay: 20
404 # Maximum number of batches to backfill per portal.
405 # If set to -1, all available messages will be backfilled.
406 max_batches: -1
407 # Optional network-specific overrides for max batches.
408 # Interpretation of this field depends on the network connector.
409 max_batches_override: {}
410
411# Settings for enabling double puppeting
412double_puppet:
413 # Servers to always allow double puppeting from.
414 # This is only for other servers and should NOT contain the server the bridge is on.
415 servers:
416 anotherserver.example.org: https://matrix.anotherserver.example.org
417 # Whether to allow client API URL discovery for other servers. When using this option,
418 # users on other servers can use double puppeting even if their server URLs aren't
419 # explicitly added to the servers map above.
420 allow_discovery: false
421 # Shared secrets for automatic double puppeting.
422 # See https://docs.mau.fi/bridges/general/double-puppeting.html for instructions.
423 secrets:
424 example.com: as_token:foobar
425
426# End-to-bridge encryption support options.
427#
428# See https://docs.mau.fi/bridges/general/end-to-bridge-encryption.html for more info.
429encryption:
430 # Whether to enable encryption at all. If false, the bridge will not function in encrypted rooms.
431 allow: false
432 # Whether to force-enable encryption in all bridged rooms.
433 default: false
434 # Whether to require all messages to be encrypted and drop any unencrypted messages.
435 require: false
436 # Whether to use MSC3202/MSC4203 instead of /sync long polling for receiving encryption-related data.
437 # This option is not yet compatible with standard Matrix servers like Synapse and should not be used.
438 # Changing this option requires updating the appservice registration file.
439 appservice: false
440 # Whether to use MSC4190 instead of appservice login to create the bridge bot device.
441 # Requires the homeserver to support MSC4190 and the device masquerading parts of MSC3202.
442 # Only relevant when using end-to-bridge encryption, required when using encryption with next-gen auth (MSC3861).
443 # Changing this option requires updating the appservice registration file.
444 msc4190: false
445 # Should the bridge bot generate a recovery key and cross-signing keys and verify itself?
446 # Note that without the latest version of MSC4190, this will fail if you reset the bridge database.
447 # The generated recovery key will be saved in the kv_store table under `recovery_key`.
448 self_sign: false
449 # Enable key sharing? If enabled, key requests for rooms where users are in will be fulfilled.
450 # You must use a client that supports requesting keys from other users to use this feature.
451 allow_key_sharing: true
452 # Pickle key for encrypting encryption keys in the bridge database.
453 # If set to generate, a random key will be generated.
454 pickle_key: generate
455 # Options for deleting megolm sessions from the bridge.
456 delete_keys:
457 # Beeper-specific: delete outbound sessions when hungryserv confirms
458 # that the user has uploaded the key to key backup.
459 delete_outbound_on_ack: false
460 # Don't store outbound sessions in the inbound table.
461 dont_store_outbound: false
462 # Ratchet megolm sessions forward after decrypting messages.
463 ratchet_on_decrypt: false
464 # Delete fully used keys (index >= max_messages) after decrypting messages.
465 delete_fully_used_on_decrypt: false
466 # Delete previous megolm sessions from same device when receiving a new one.
467 delete_prev_on_new_session: false
468 # Delete megolm sessions received from a device when the device is deleted.
469 delete_on_device_delete: false
470 # Periodically delete megolm sessions when 2x max_age has passed since receiving the session.
471 periodically_delete_expired: false
472 # Delete inbound megolm sessions that don't have the received_at field used for
473 # automatic ratcheting and expired session deletion. This is meant as a migration
474 # to delete old keys prior to the bridge update.
475 delete_outdated_inbound: false
476 # What level of device verification should be required from users?
477 #
478 # Valid levels:
479 # unverified - Send keys to all device in the room.
480 # cross-signed-untrusted - Require valid cross-signing, but trust all cross-signing keys.
481 # cross-signed-tofu - Require valid cross-signing, trust cross-signing keys on first use (and reject changes).
482 # cross-signed-verified - Require valid cross-signing, plus a valid user signature from the bridge bot.
483 # Note that creating user signatures from the bridge bot is not currently possible.
484 # verified - Require manual per-device verification
485 # (currently only possible by modifying the `trust` column in the `crypto_device` database table).
486 verification_levels:
487 # Minimum level for which the bridge should send keys to when bridging messages from the remote network to Matrix.
488 receive: unverified
489 # Minimum level that the bridge should accept for incoming Matrix messages.
490 send: unverified
491 # Minimum level that the bridge should require for accepting key requests.
492 share: cross-signed-tofu
493 # Options for Megolm room key rotation. These options allow you to configure the m.room.encryption event content.
494 # See https://spec.matrix.org/v1.10/client-server-api/#mroomencryption for more information about that event.
495 rotation:
496 # Enable custom Megolm room key rotation settings. Note that these
497 # settings will only apply to rooms created after this option is set.
498 enable_custom: false
499 # The maximum number of milliseconds a session should be used
500 # before changing it. The Matrix spec recommends 604800000 (a week)
501 # as the default.
502 milliseconds: 604800000
503 # The maximum number of messages that should be sent with a given a
504 # session before changing it. The Matrix spec recommends 100 as the
505 # default.
506 messages: 100
507 # Disable rotating keys when a user's devices change?
508 # You should not enable this option unless you understand all the implications.
509 disable_device_change_key_rotation: false
510
511# Logging config. See https://github.com/tulir/zeroconfig for details.
512logging:
513 min_level: debug
514 writers:
515 - type: stdout
516 format: pretty-colored
517 - type: file
518 format: json
519 filename: ./logs/bridge.log
520 max_size: 100
521 max_backups: 10
522 compress: false