fix: make bridge registrations agree with the secret-sourced config
cc-ci/testme cc-ci: success

This commit is contained in:
autonomic-bot
2026-11-20 06:08:17 +00:00
parent bf8c126a00
commit dfdfa6bff2
9 changed files with 337 additions and 546 deletions
+8 -4
View File
@@ -211,13 +211,16 @@ RETENTION_MAX_LIFETIME=4w
#COMPOSE_FILE="$COMPOSE_FILE:compose.telegram.yml"
#APP_SERVICE_BOT_USERNAME=telegrambot
#APP_SERVICE_DISPLAY_NAME="Telegram bridge bot"
#APP_SERVICE_ID=
#APP_SERVICE_ID=telegrambot
#HOMESERVER_DOMAIN=$DOMAIN
#HOMESERVER_URL=https://$DOMAIN
#VERIFY_SSL=false
#ENABLE_ENCRYPTION=true
#TELEGRAM_APP_ID=
#TELEGRAM_BRIDGE_PERMISSIONS="{ \"*\": \"relaybot\", \"@foo:matrix.example.com\": \"admin\" }"
# NOTE (bridgev2): a wildcard-only permissions map is rejected by the bridge; include at least
# one real domain or mxid entry. The legacy "relaybot" level no longer exists upstream -
# use "relay" together with bridge relay mode instead.
#TELEGRAM_BRIDGE_PERMISSIONS="{ \"*\": \"relay\", \"matrix.example.com\": \"user\" }"
#TELEGRAM_SYNC_CHANNEL_MEMBERS=true
#SECRET_TELEGRAM_DB_PASSWORD_VERSION=v1
#SECRET_TELEGRAM_API_HASH_VERSION=v1
@@ -238,8 +241,9 @@ RETENTION_MAX_LIFETIME=4w
#COMPOSE_FILE="$COMPOSE_FILE:compose.signal.yml"
#SIGNAL_ENABLE_ENCRYPTION=true
#SIGNAL_DEFAULT_ENCRYPTION=true
#SIGNAL_BRIDGE_PERMISSIONS="{ \"*\": \"relay\" }"
#SECRET_SIGNAL_AS_TOKEN_VERSION=v1
# NOTE (bridgev2): a wildcard-only permissions map is rejected by the bridge; include at least
# one real domain or mxid entry.
#SIGNAL_BRIDGE_PERMISSIONS="{ \"*\": \"relay\", \"matrix.example.com\": \"user\" }"
#SECRET_SIGNAL_DB_PASSWORD_VERSION=v1
#SECRET_SIGNAL_HS_TOKEN_VERSION=v1
#SECRET_SIGNAL_PICKLE_KEY_VERSION=v1