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