gekürzt
This commit is contained in:
		@ -4,23 +4,13 @@ homeserver:
 | 
			
		||||
    address: http://synapse:8008
 | 
			
		||||
    # The domain of the homeserver (also known as server_name, used for MXIDs, etc).
 | 
			
		||||
    domain: matrix.server-nb.de
 | 
			
		||||
    
 | 
			
		||||
    # What software is the homeserver running?
 | 
			
		||||
    # Standard Matrix homeservers like Synapse, Dendrite and Conduit should just use "standard" here.
 | 
			
		||||
    software: standard
 | 
			
		||||
    # 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.
 | 
			
		||||
    # The bridge will use the appservice as_token to authorize requests.
 | 
			
		||||
    status_endpoint: null
 | 
			
		||||
    # Endpoint for reporting per-message status.
 | 
			
		||||
    message_send_checkpoint_endpoint: null
 | 
			
		||||
    # Does the homeserver support https://github.com/matrix-org/matrix-spec-proposals/pull/2246?
 | 
			
		||||
    async_media: false
 | 
			
		||||
    # Should the bridge use a websocket for connecting to the homeserver?
 | 
			
		||||
    # The server side is currently not documented anywhere and is only implemented by mautrix-wsproxy,
 | 
			
		||||
    # mautrix-asmux (deprecated), and hungryserv (proprietary).
 | 
			
		||||
    websocket: false
 | 
			
		||||
    # How often should the websocket be pinged? Pinging will be disabled if this is zero.
 | 
			
		||||
    ping_interval_seconds: 0
 | 
			
		||||
 | 
			
		||||
# Application service host/registration related details.
 | 
			
		||||
@ -28,26 +18,15 @@ homeserver:
 | 
			
		||||
appservice:
 | 
			
		||||
    # The address that the homeserver can use to connect to this appservice.
 | 
			
		||||
    address: http://mautrix-whatsapp:29318
 | 
			
		||||
    
 | 
			
		||||
    # The hostname and port where this appservice should listen.
 | 
			
		||||
    hostname: 0.0.0.0
 | 
			
		||||
    port: 29318
 | 
			
		||||
    
 | 
			
		||||
    # Database config.
 | 
			
		||||
    database:
 | 
			
		||||
        # The database type. "sqlite3-fk-wal" and "postgres" are supported.
 | 
			
		||||
        type: postgres
 | 
			
		||||
        # The database URI.
 | 
			
		||||
        #   SQLite: A raw file path is supported, but `file:<path>?_txlock=immediate` is recommended.
 | 
			
		||||
        #           https://github.com/mattn/go-sqlite3#connection-string
 | 
			
		||||
        #   Postgres: Connection string. For example, postgres://user:password@host/database?sslmode=disable
 | 
			
		||||
        #             To connect via Unix socket, use something like postgres:///dbname?host=/var/run/postgresql
 | 
			
		||||
        uri: postgres://whatsapp:jgzqnGCq3KY28C@postgres-whatsapp:5432/whatsapp?sslmode=disable
 | 
			
		||||
        # Maximum number of connections. Mostly relevant for Postgres.
 | 
			
		||||
        max_open_conns: 20
 | 
			
		||||
        max_idle_conns: 2
 | 
			
		||||
        # Maximum connection idle time and lifetime before they're closed. Disabled if null.
 | 
			
		||||
        # Parsed with https://pkg.go.dev/time#ParseDuration
 | 
			
		||||
        max_conn_idle_time: null
 | 
			
		||||
        max_conn_lifetime: null
 | 
			
		||||
    
 | 
			
		||||
@ -114,7 +93,7 @@ bridge:
 | 
			
		||||
    displayname_template: "{{.FullName}} (WA)"
 | 
			
		||||
    # Should the bridge create a space for each logged-in user and add bridged rooms to it?
 | 
			
		||||
    # Users who logged in before turning this on should run `!wa sync space` to create and fill the space for the first time.
 | 
			
		||||
    personal_filtering_spaces: true
 | 
			
		||||
    personal_filtering_spaces: false
 | 
			
		||||
    # Should the bridge send a read receipt from the bridge bot when a message has been sent to WhatsApp?
 | 
			
		||||
    delivery_receipts: false
 | 
			
		||||
    # Whether the bridge should send the message status as a custom com.beeper.message_send_status event.
 | 
			
		||||
 | 
			
		||||
		Reference in New Issue
	
	Block a user