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