From d3b1060428aed69f934835d56a954fc9545070f6 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Tue, 17 Sep 2024 16:04:06 +0300 Subject: [PATCH] Fix Gmessages regression (missing homeserver.address and homeserver.domain configuration) f9705b3323863bfcb85426 reworked the configuration and missed wiring these to the existing variables. --- .../matrix-bridge-mautrix-gmessages/templates/config.yaml.j2 | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/roles/custom/matrix-bridge-mautrix-gmessages/templates/config.yaml.j2 b/roles/custom/matrix-bridge-mautrix-gmessages/templates/config.yaml.j2 index 89000de86..a645d6d0f 100644 --- a/roles/custom/matrix-bridge-mautrix-gmessages/templates/config.yaml.j2 +++ b/roles/custom/matrix-bridge-mautrix-gmessages/templates/config.yaml.j2 @@ -150,9 +150,9 @@ homeserver: # The address that this appservice can use to connect to the homeserver. # Local addresses without HTTPS are generally recommended when the bridge is running on the same machine, # but https also works if they run on different machines. - address: http://example.localhost:8008 + address: {{ matrix_mautrix_gmessages_homeserver_address | to_json }} # The domain of the homeserver (also known as server_name, used for MXIDs, etc). - domain: example.com + domain: {{ matrix_mautrix_gmessages_homeserver_domain | to_json }} # What software is the homeserver running? # Standard Matrix homeservers like Synapse, Dendrite and Conduit should just use "standard" here.