update config file
This commit is contained in:
parent
109458b3c1
commit
657c30931a
@ -5,8 +5,9 @@ homeserver:
|
|||||||
# The domain of the homeserver (for MXIDs, etc).
|
# The domain of the homeserver (for MXIDs, etc).
|
||||||
domain: "{{ getenv "SERVER_DOMAIN" }}"
|
domain: "{{ getenv "SERVER_DOMAIN" }}"
|
||||||
|
|
||||||
# Is the homeserver actually mautrix-asmux?
|
# What software is the homeserver running?
|
||||||
asmux: false
|
# Standard Matrix homeservers like Synapse, Dendrite and Conduit should just use "standard" here.
|
||||||
|
software: standard
|
||||||
# The URL to push real-time bridge status to.
|
# The URL to push real-time bridge status to.
|
||||||
# If set, the bridge will make POST requests to this URL whenever a user's whatsapp connection state changes.
|
# If set, the bridge will make POST requests to this URL whenever a user's whatsapp connection state changes.
|
||||||
# The bridge will use the appservice as_token to authorize requests.
|
# The bridge will use the appservice as_token to authorize requests.
|
||||||
@ -23,7 +24,7 @@ appservice:
|
|||||||
address: http://{{getenv "HOSTNAME"}}:29318
|
address: http://{{getenv "HOSTNAME"}}:29318
|
||||||
|
|
||||||
# The hostname and port where this appservice should listen.
|
# The hostname and port where this appservice should listen.
|
||||||
hostname: 0.0.0.0
|
hostname: "::"
|
||||||
port: 29318
|
port: 29318
|
||||||
|
|
||||||
# Database config.
|
# Database config.
|
||||||
@ -57,7 +58,12 @@ appservice:
|
|||||||
# Whether or not to receive ephemeral events via appservice transactions.
|
# Whether or not to receive ephemeral events via appservice transactions.
|
||||||
# Requires MSC2409 support (i.e. Synapse 1.22+).
|
# Requires MSC2409 support (i.e. Synapse 1.22+).
|
||||||
# You should disable bridge -> sync_with_custom_puppets when this is enabled.
|
# You should disable bridge -> sync_with_custom_puppets when this is enabled.
|
||||||
ephemeral_events: false
|
ephemeral_events: true
|
||||||
|
|
||||||
|
# Should incoming events be handled asynchronously?
|
||||||
|
# This may be necessary for large public instances with lots of messages going through.
|
||||||
|
# However, messages will not be guaranteed to be bridged in the same order they were sent in.
|
||||||
|
async_transactions: false
|
||||||
|
|
||||||
# Authentication tokens for AS <-> HS communication. Autogenerated; do not modify.
|
# Authentication tokens for AS <-> HS communication. Autogenerated; do not modify.
|
||||||
as_token: "{{ getenv "AS_TOKEN" -}}"
|
as_token: "{{ getenv "AS_TOKEN" -}}"
|
||||||
@ -148,6 +154,12 @@ bridge:
|
|||||||
# provisioning endpoint is used or when a message comes in from that
|
# provisioning endpoint is used or when a message comes in from that
|
||||||
# chat.
|
# chat.
|
||||||
max_initial_conversations: -1
|
max_initial_conversations: -1
|
||||||
|
# If this value is greater than 0, then if the conversation's last
|
||||||
|
# message was more than this number of hours ago, then the conversation
|
||||||
|
# will automatically be marked it as read.
|
||||||
|
# Conversations that have a last message that is less than this number
|
||||||
|
# of hours ago will have their unread status synced from WhatsApp.
|
||||||
|
unread_hours_threshold: 0
|
||||||
# Settings for immediate backfills. These backfills should generally be
|
# Settings for immediate backfills. These backfills should generally be
|
||||||
# small and their main purpose is to populate each of the initial chats
|
# small and their main purpose is to populate each of the initial chats
|
||||||
# (as configured by max_initial_conversations) with a few messages so
|
# (as configured by max_initial_conversations) with a few messages so
|
||||||
@ -192,7 +204,7 @@ bridge:
|
|||||||
# Should Matrix users leaving groups be bridged to WhatsApp?
|
# Should Matrix users leaving groups be bridged to WhatsApp?
|
||||||
bridge_matrix_leave: true
|
bridge_matrix_leave: true
|
||||||
# Should the bridge sync with double puppeting to receive EDUs that aren't normally sent to appservices.
|
# Should the bridge sync with double puppeting to receive EDUs that aren't normally sent to appservices.
|
||||||
sync_with_custom_puppets: true
|
sync_with_custom_puppets: false
|
||||||
# Should the bridge update the m.direct account data event when double puppeting is enabled.
|
# Should the bridge update the m.direct account data event when double puppeting is enabled.
|
||||||
# Note that updating the m.direct event is not atomic (except with mautrix-asmux)
|
# Note that updating the m.direct event is not atomic (except with mautrix-asmux)
|
||||||
# and is therefore prone to race conditions.
|
# and is therefore prone to race conditions.
|
||||||
@ -230,7 +242,10 @@ bridge:
|
|||||||
login_shared_secret_map:
|
login_shared_secret_map:
|
||||||
example.com: foobar
|
example.com: foobar
|
||||||
# Should the bridge explicitly set the avatar and room name for private chat portal rooms?
|
# Should the bridge explicitly set the avatar and room name for private chat portal rooms?
|
||||||
|
# This is implicitly enabled in encrypted rooms.
|
||||||
private_chat_portal_meta: false
|
private_chat_portal_meta: false
|
||||||
|
# Should group members be synced in parallel? This makes member sync faster
|
||||||
|
parallel_member_sync: false
|
||||||
# Should Matrix m.notice-type messages be bridged?
|
# Should Matrix m.notice-type messages be bridged?
|
||||||
bridge_notices: true
|
bridge_notices: true
|
||||||
# Set this to true to tell the bridge to re-send m.bridge events to all rooms on the next run.
|
# Set this to true to tell the bridge to re-send m.bridge events to all rooms on the next run.
|
||||||
@ -273,6 +288,9 @@ bridge:
|
|||||||
# Should the bridge never send alerts to the bridge management room?
|
# Should the bridge never send alerts to the bridge management room?
|
||||||
# These are mostly things like the user being logged out.
|
# These are mostly things like the user being logged out.
|
||||||
disable_bridge_alerts: false
|
disable_bridge_alerts: false
|
||||||
|
# Should the bridge stop if the WhatsApp server says another user connected with the same session?
|
||||||
|
# This is only safe on single-user bridges.
|
||||||
|
crash_on_stream_replaced: false
|
||||||
# Should the bridge detect URLs in outgoing messages, ask the homeserver to generate a preview,
|
# Should the bridge detect URLs in outgoing messages, ask the homeserver to generate a preview,
|
||||||
# and send it to WhatsApp? URL previews can always be sent using the `com.beeper.linkpreviews`
|
# and send it to WhatsApp? URL previews can always be sent using the `com.beeper.linkpreviews`
|
||||||
# key in the event content even if this is disabled.
|
# key in the event content even if this is disabled.
|
||||||
@ -280,6 +298,12 @@ bridge:
|
|||||||
# Send captions in the same message as images. This will send data compatible with both MSC2530 and MSC3552.
|
# Send captions in the same message as images. This will send data compatible with both MSC2530 and MSC3552.
|
||||||
# This is currently not supported in most clients.
|
# This is currently not supported in most clients.
|
||||||
caption_in_message: false
|
caption_in_message: false
|
||||||
|
# Should polls be sent using MSC3381 event types? This should either be 1 for original polls MSC,
|
||||||
|
# 2 for the updated MSC as of November 2022, or 0 to use legacy m.room.message (which doesn't support voting).
|
||||||
|
extev_polls: 0
|
||||||
|
# Should Matrix edits be bridged to WhatsApp edits?
|
||||||
|
# Official WhatsApp clients don't render edits yet, but once they do, the bridge should work with them right away.
|
||||||
|
send_whatsapp_edits: false
|
||||||
# Maximum time for handling Matrix events. Duration strings formatted for https://pkg.go.dev/time#ParseDuration
|
# Maximum time for handling Matrix events. Duration strings formatted for https://pkg.go.dev/time#ParseDuration
|
||||||
# Null means there's no enforced timeout.
|
# Null means there's no enforced timeout.
|
||||||
message_handling_timeout:
|
message_handling_timeout:
|
||||||
@ -314,8 +338,9 @@ bridge:
|
|||||||
allow: true
|
allow: true
|
||||||
# Default to encryption, force-enable encryption in all portals the bridge creates
|
# Default to encryption, force-enable encryption in all portals the bridge creates
|
||||||
# This will cause the bridge bot to be in private chats for the encryption to work properly.
|
# This will cause the bridge bot to be in private chats for the encryption to work properly.
|
||||||
# It is recommended to also set private_chat_portal_meta to true when using this.
|
|
||||||
default: true
|
default: true
|
||||||
|
# Whether to use MSC2409/MSC3202 instead of /sync long polling for receiving encryption-related data.
|
||||||
|
appservice: false
|
||||||
# Require encryption, drop any unencrypted messages.
|
# Require encryption, drop any unencrypted messages.
|
||||||
require: false
|
require: false
|
||||||
# Enable key sharing? If enabled, key requests for rooms where users are in will be fulfilled.
|
# Enable key sharing? If enabled, key requests for rooms where users are in will be fulfilled.
|
||||||
@ -378,6 +403,7 @@ bridge:
|
|||||||
"{{ getenv "SERVER_DOMAIN" }}": user
|
"{{ getenv "SERVER_DOMAIN" }}": user
|
||||||
"{{ getenv "ADMIN_USER" }}": admin
|
"{{ getenv "ADMIN_USER" }}": admin
|
||||||
|
|
||||||
|
|
||||||
# Settings for relay mode
|
# Settings for relay mode
|
||||||
relay:
|
relay:
|
||||||
# Whether relay mode should be allowed. If allowed, `!wa set-relay` can be used to turn any
|
# Whether relay mode should be allowed. If allowed, `!wa set-relay` can be used to turn any
|
||||||
|
Loading…
Reference in New Issue
Block a user