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
53
54# Config options that affect the central bridge module.
55bridge:
56 # The prefix for commands. Only required in non-management rooms.
57 command_prefix: '!meta'
58 # Should the bridge create a space for each login containing the rooms that account is in?
59 personal_filtering_spaces: true
60 # Whether the bridge should set names and avatars explicitly for DM portals.
61 # This is only necessary when using clients that don't support MSC4171.
62 private_chat_portal_meta: true
63 # Should events be handled asynchronously within portal rooms?
64 # If true, events may end up being out of order, but slow events won't block other ones.
65 # This is not yet safe to use.
66 async_events: false
67 # Should every user have their own portals rather than sharing them?
68 # By default, users who are in the same group on the remote network will be
69 # in the same Matrix room bridged to that group. If this is set to true,
70 # every user will get their own Matrix room instead.
71 # SETTING THIS IS IRREVERSIBLE AND POTENTIALLY DESTRUCTIVE IF PORTALS ALREADY EXIST.
72 split_portals: false
73 # Should the bridge resend `m.bridge` events to all portals on startup?
74 resend_bridge_info: false
75 # Should `m.bridge` events be sent without a state key?
76 # By default, the bridge uses a unique key that won't conflict with other bridges.
77 no_bridge_info_state_key: false
78 # Should bridge connection status be sent to the management room as `m.notice` events?
79 # These contain the same data that can be posted to an external HTTP server using homeserver -> status_endpoint.
80 # Allowed values: none, errors, all
81 bridge_status_notices: errors
82 # How long after an unknown error should the bridge attempt a full reconnect?
83 # Must be at least 1 minute. The bridge will add an extra ±20% jitter to this value.
84 unknown_error_auto_reconnect: null
85
86 # Should leaving Matrix rooms be bridged as leaving groups on the remote network?
87 bridge_matrix_leave: false
88 # Should `m.notice` messages be bridged?
89 bridge_notices: false
90 # Should room tags only be synced when creating the portal? Tags mean things like favorite/pin and archive/low priority.
91 # Tags currently can't be synced back to the remote network, so a continuous sync means tagging from Matrix will be undone.
92 tag_only_on_create: true
93 # List of tags to allow bridging. If empty, no tags will be bridged.
94 only_bridge_tags: [m.favourite, m.lowpriority]
95 # Should room mute status only be synced when creating the portal?
96 # Like tags, mutes can't currently be synced back to the remote network.
97 mute_only_on_create: true
98 # Should the bridge check the db to ensure that incoming events haven't been handled before
99 deduplicate_matrix_messages: false
100 # Should cross-room reply metadata be bridged?
101 # Most Matrix clients don't support this and servers may reject such messages too.
102 cross_room_replies: false
103 # If a state event fails to bridge, should the bridge revert any state changes made by that event?
104 revert_failed_state_changes: false
105 # In portals with no relay set, should Matrix users be kicked if they're
106 # not logged into an account that's in the remote chat?
107 kick_matrix_users: true
108
109 # What should be done to portal rooms when a user logs out or is logged out?
110 # Permitted values:
111 # nothing - Do nothing, let the user stay in the portals
112 # kick - Remove the user from the portal rooms, but don't delete them
113 # unbridge - Remove all ghosts in the room and disassociate it from the remote chat
114 # delete - Remove all ghosts and users from the room (i.e. delete it)
115 cleanup_on_logout:
116 # Should cleanup on logout be enabled at all?
117 enabled: false
118 # Settings for manual logouts (explicitly initiated by the Matrix user)
119 manual:
120 # Action for private portals which will never be shared with other Matrix users.
121 private: nothing
122 # Action for portals with a relay user configured.
123 relayed: nothing
124 # Action for portals which may be shared, but don't currently have any other Matrix users.
125 shared_no_users: nothing
126 # Action for portals which have other logged-in Matrix users.
127 shared_has_users: nothing
128 # Settings for credentials being invalidated (initiated by the remote network, possibly through user action).
129 # Keys have the same meanings as in the manual section.
130 bad_credentials:
131 private: nothing
132 relayed: nothing
133 shared_no_users: nothing
134 shared_has_users: nothing
135
136 # Settings for relay mode
137 relay:
138 # Whether relay mode should be allowed. If allowed, the set-relay command can be used to turn any
139 # authenticated user into a relaybot for that chat.
140 enabled: false
141 # Should only admins be allowed to set themselves as relay users?
142 # If true, non-admins can only set users listed in default_relays as relays in a room.
143 admin_only: true
144 # List of user login IDs which anyone can set as a relay, as long as the relay user is in the room.
145 default_relays: []
146 # The formats to use when sending messages via the relaybot.
147 # Available variables:
148 # .Sender.UserID - The Matrix user ID of the sender.
149 # .Sender.Displayname - The display name of the sender (if set).
150 # .Sender.RequiresDisambiguation - Whether the sender's name may be confused with the name of another user in the room.
151 # .Sender.DisambiguatedName - The disambiguated name of the sender. This will be the displayname if set,
152 # plus the user ID in parentheses if the displayname is not unique.
153 # If the displayname is not set, this is just the user ID.
154 # .Message - The `formatted_body` field of the message.
155 # .Caption - The `formatted_body` field of the message, if it's a caption. Otherwise an empty string.
156 # .FileName - The name of the file being sent.
157 message_formats:
158 m.text: "<b>{{ .Sender.DisambiguatedName }}</b>: {{ .Message }}"
159 m.notice: "<b>{{ .Sender.DisambiguatedName }}</b>: {{ .Message }}"
160 m.emote: "* <b>{{ .Sender.DisambiguatedName }}</b> {{ .Message }}"
161 m.file: "<b>{{ .Sender.DisambiguatedName }}</b> sent a file{{ if .Caption }}: {{ .Caption }}{{ end }}"
162 m.image: "<b>{{ .Sender.DisambiguatedName }}</b> sent an image{{ if .Caption }}: {{ .Caption }}{{ end }}"
163 m.audio: "<b>{{ .Sender.DisambiguatedName }}</b> sent an audio file{{ if .Caption }}: {{ .Caption }}{{ end }}"
164 m.video: "<b>{{ .Sender.DisambiguatedName }}</b> sent a video{{ if .Caption }}: {{ .Caption }}{{ end }}"
165 m.location: "<b>{{ .Sender.DisambiguatedName }}</b> sent a location{{ if .Caption }}: {{ .Caption }}{{ end }}"
166 # For networks that support per-message displaynames (i.e. Slack and Discord), the template for those names.
167 # This has all the Sender variables available under message_formats (but without the .Sender prefix).
168 # Note that you need to manually remove the displayname from message_formats above.
169 displayname_format: "{{ .DisambiguatedName }}"
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:29319
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: 29319
253
254 # The unique ID of this appservice.
255 id: meta
256 # Appservice bot details.
257 bot:
258 # Username of the appservice bot.
259 username: metabot
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: Meta bridge bot
263 avatar: mxc://maunium.net/DxpVrwwzPUwaUSazpsjXgcKB
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: meta_{{.}}
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
298# Segment-compatible analytics endpoint for tracking some events, like provisioning API login and encryption errors.
299analytics:
300 # API key to send with tracking requests. Tracking is disabled if this is null.
301 token: null
302 # Address to send tracking requests to.
303 url: https://api.segment.io/v1/track
304 # Optional user ID for tracking events. If null, defaults to using Matrix user ID.
305 user_id: null
306
307# Settings for provisioning API
308provisioning:
309 # Shared secret for authentication. If set to "generate" or null, a random secret will be generated,
310 # or if set to "disable", the provisioning API will be disabled. Must be at least 16 characters.
311 shared_secret: generate
312 # Whether to allow provisioning API requests to be authed using Matrix access tokens.
313 # This follows the same rules as double puppeting to determine which server to contact to check the token,
314 # which means that by default, it only works for users on the same server as the bridge.
315 allow_matrix_auth: true
316 # Enable debug API at /debug with provisioning authentication.
317 debug_endpoints: false
318 # Enable session transfers between bridges. Note that this only validates Matrix or shared secret
319 # auth before passing live network client credentials down in the response.
320 enable_session_transfers: false
321
322# Some networks require publicly accessible media download links (e.g. for user avatars when using Discord webhooks).
323# These settings control whether the bridge will provide such public media access.
324public_media:
325 # Should public media be enabled at all?
326 # The public_address field under the appservice section MUST be set when enabling public media.
327 enabled: false
328 # A key for signing public media URLs.
329 # If set to "generate", a random key will be generated.
330 signing_key: generate
331 # Number of seconds that public media URLs are valid for.
332 # If set to 0, URLs will never expire.
333 expiry: 0
334 # Length of hash to use for public media URLs. Must be between 0 and 32.
335 hash_length: 32
336 # The path prefix for generated URLs. Note that this will NOT change the path where media is actually served.
337 # If you change this, you must configure your reverse proxy to rewrite the path accordingly.
338 path_prefix: /_mautrix/publicmedia
339 # Should the bridge store media metadata in the database in order to support encrypted media and generate shorter URLs?
340 # If false, the generated URLs will just have the MXC URI and a HMAC signature.
341 # The hash_length field will be used to decide the length of the generated URL.
342 # This also allows invalidating URLs by deleting the database entry.
343 use_database: false
344
345# Settings for converting remote media to custom mxc:// URIs instead of reuploading.
346# More details can be found at https://docs.mau.fi/bridges/go/discord/direct-media.html
347direct_media:
348 # Should custom mxc:// URIs be used instead of reuploading media?
349 enabled: false
350 # The server name to use for the custom mxc:// URIs.
351 # This server name will effectively be a real Matrix server, it just won't implement anything other than media.
352 # You must either set up .well-known delegation from this domain to the bridge, or proxy the domain directly to the bridge.
353 server_name: discord-media.example.com
354 # Optionally a custom .well-known response. This defaults to `server_name:443`
355 well_known_response:
356 # Optionally specify a custom prefix for the media ID part of the MXC URI.
357 media_id_prefix:
358 # If the remote network supports media downloads over HTTP, then the bridge will use MSC3860/MSC3916
359 # media download redirects if the requester supports it. Optionally, you can force redirects
360 # and not allow proxying at all by setting this to false.
361 # This option does nothing if the remote network does not support media downloads over HTTP.
362 allow_proxy: true
363 # Matrix server signing key to make the federation tester pass, same format as synapse's .signing.key file.
364 # This key is also used to sign the mxc:// URIs to ensure only the bridge can generate them.
365 server_key: generate
366
367# Settings for backfilling messages.
368# Note that the exact way settings are applied depends on the network connector.
369# See https://docs.mau.fi/bridges/general/backfill.html for more details.
370backfill:
371 # Whether to do backfilling at all.
372 enabled: false
373 # Maximum number of messages to backfill in empty rooms.
374 max_initial_messages: 50
375 # Maximum number of missed messages to backfill after bridge restarts.
376 max_catchup_messages: 500
377 # If a backfilled chat is older than this number of hours,
378 # mark it as read even if it's unread on the remote network.
379 unread_hours_threshold: 720
380 # Settings for backfilling threads within other backfills.
381 threads:
382 # Maximum number of messages to backfill in a new thread.
383 max_initial_messages: 50
384 # Settings for the backwards backfill queue. This only applies when connecting to
385 # Beeper as standard Matrix servers don't support inserting messages into history.
386 queue:
387 # Should the backfill queue be enabled?
388 enabled: false
389 # Number of messages to backfill in one batch.
390 batch_size: 100
391 # Delay between batches in seconds.
392 batch_delay: 20
393 # Maximum number of batches to backfill per portal.
394 # If set to -1, all available messages will be backfilled.
395 max_batches: -1
396 # Optional network-specific overrides for max batches.
397 # Interpretation of this field depends on the network connector.
398 max_batches_override: {}
399
400# Settings for enabling double puppeting
401double_puppet:
402 # Servers to always allow double puppeting from.
403 # This is only for other servers and should NOT contain the server the bridge is on.
404 servers:
405 anotherserver.example.org: https://matrix.anotherserver.example.org
406 # Whether to allow client API URL discovery for other servers. When using this option,
407 # users on other servers can use double puppeting even if their server URLs aren't
408 # explicitly added to the servers map above.
409 allow_discovery: false
410 # Shared secrets for automatic double puppeting.
411 # See https://docs.mau.fi/bridges/general/double-puppeting.html for instructions.
412 secrets:
413 example.com: as_token:foobar
414
415# End-to-bridge encryption support options.
416#
417# See https://docs.mau.fi/bridges/general/end-to-bridge-encryption.html for more info.
418encryption:
419 # Whether to enable encryption at all. If false, the bridge will not function in encrypted rooms.
420 allow: false
421 # Whether to force-enable encryption in all bridged rooms.
422 default: false
423 # Whether to require all messages to be encrypted and drop any unencrypted messages.
424 require: false
425 # Whether to use MSC3202/MSC4203 instead of /sync long polling for receiving encryption-related data.
426 # This option is not yet compatible with standard Matrix servers like Synapse and should not be used.
427 # Changing this option requires updating the appservice registration file.
428 appservice: false
429 # Whether to use MSC4190 instead of appservice login to create the bridge bot device.
430 # Requires the homeserver to support MSC4190 and the device masquerading parts of MSC3202.
431 # Only relevant when using end-to-bridge encryption, required when using encryption with next-gen auth (MSC3861).
432 # Changing this option requires updating the appservice registration file.
433 msc4190: false
434 # Should the bridge bot generate a recovery key and cross-signing keys and verify itself?
435 # Note that without the latest version of MSC4190, this will fail if you reset the bridge database.
436 # The generated recovery key will be saved in the kv_store table under `recovery_key`.
437 self_sign: false
438 # Enable key sharing? If enabled, key requests for rooms where users are in will be fulfilled.
439 # You must use a client that supports requesting keys from other users to use this feature.
440 allow_key_sharing: true
441 # Pickle key for encrypting encryption keys in the bridge database.
442 # If set to generate, a random key will be generated.
443 pickle_key: generate
444 # Options for deleting megolm sessions from the bridge.
445 delete_keys:
446 # Beeper-specific: delete outbound sessions when hungryserv confirms
447 # that the user has uploaded the key to key backup.
448 delete_outbound_on_ack: false
449 # Don't store outbound sessions in the inbound table.
450 dont_store_outbound: false
451 # Ratchet megolm sessions forward after decrypting messages.
452 ratchet_on_decrypt: false
453 # Delete fully used keys (index >= max_messages) after decrypting messages.
454 delete_fully_used_on_decrypt: false
455 # Delete previous megolm sessions from same device when receiving a new one.
456 delete_prev_on_new_session: false
457 # Delete megolm sessions received from a device when the device is deleted.
458 delete_on_device_delete: false
459 # Periodically delete megolm sessions when 2x max_age has passed since receiving the session.
460 periodically_delete_expired: false
461 # Delete inbound megolm sessions that don't have the received_at field used for
462 # automatic ratcheting and expired session deletion. This is meant as a migration
463 # to delete old keys prior to the bridge update.
464 delete_outdated_inbound: false
465 # What level of device verification should be required from users?
466 #
467 # Valid levels:
468 # unverified - Send keys to all device in the room.
469 # cross-signed-untrusted - Require valid cross-signing, but trust all cross-signing keys.
470 # cross-signed-tofu - Require valid cross-signing, trust cross-signing keys on first use (and reject changes).
471 # cross-signed-verified - Require valid cross-signing, plus a valid user signature from the bridge bot.
472 # Note that creating user signatures from the bridge bot is not currently possible.
473 # verified - Require manual per-device verification
474 # (currently only possible by modifying the `trust` column in the `crypto_device` database table).
475 verification_levels:
476 # Minimum level for which the bridge should send keys to when bridging messages from the remote network to Matrix.
477 receive: unverified
478 # Minimum level that the bridge should accept for incoming Matrix messages.
479 send: unverified
480 # Minimum level that the bridge should require for accepting key requests.
481 share: cross-signed-tofu
482 # Options for Megolm room key rotation. These options allow you to configure the m.room.encryption event content.
483 # See https://spec.matrix.org/v1.10/client-server-api/#mroomencryption for more information about that event.
484 rotation:
485 # Enable custom Megolm room key rotation settings. Note that these
486 # settings will only apply to rooms created after this option is set.
487 enable_custom: false
488 # The maximum number of milliseconds a session should be used
489 # before changing it. The Matrix spec recommends 604800000 (a week)
490 # as the default.
491 milliseconds: 604800000
492 # The maximum number of messages that should be sent with a given a
493 # session before changing it. The Matrix spec recommends 100 as the
494 # default.
495 messages: 100
496 # Disable rotating keys when a user's devices change?
497 # You should not enable this option unless you understand all the implications.
498 disable_device_change_key_rotation: false
499
500# Logging config. See https://github.com/tulir/zeroconfig for details.
501logging:
502 min_level: debug
503 writers:
504 - type: stdout
505 format: pretty-colored
506 - type: file
507 format: json
508 filename: ./logs/bridge.log
509 max_size: 100
510 max_backups: 10
511 compress: false