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