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