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