From 8f9c66e95d7d2e73d3c0b03d4832d74a79d79b19 Mon Sep 17 00:00:00 2001 From: Simon Date: Wed, 21 Aug 2024 18:37:06 +0200 Subject: [PATCH] Update Bridge Readme --- README.md | 15 ++++++++------- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/README.md b/README.md index 0b43271..a423af4 100644 --- a/README.md +++ b/README.md @@ -45,12 +45,17 @@ See [`#27`](https://git.coopcloud.tech/coop-cloud/matrix-synapse/pulls/27) for m You'll need to deploy something like [this](https://git.autonomic.zone/ruangrupa/well-known-uris). This could be implemented in this recipe but we haven't merged it in yet. Change sets are welcome. +## Bridges +For all Bridges: +- Setting it up is a bit of a chicken/egg & chasing cats moment. +- Make sure to uncomment `APP_SERVICES_ENABLED`, `HOMESERVER_URL`, `HOMESERVER_DOMAIN`, `compose.shared_secret_auth.yml`, `SHARED_SECRET_AUTH_ENABLED` and `SECRET_SHARED_SECRET_AUTH_VERSION` +- include the registration in synapse, e.g. `APP_SERVICE_CONFIGS="[\"/telegram-data/registration.yaml\"]"` +- and set yourself as admin, e.g.: `TELEGRAM_BRIDGE_PERMISSIONS="{ \"*\": \"relaybot\", \"@akadmin:example.com\": \"admin\"}"` + ### Telegram bridging > WIP docs -Setting it up is a bit of a chicken/egg & chasing cats moment. - You need to get your bot setup on the telegram side first by creating a [telegram app](https://my.telegram.org/apps) and a [telegram bot](https://docs.mau.fi/bridges/python/telegram/relay-bot.html#setup) and have these values: ``` @@ -59,11 +64,6 @@ api_hash: ... telegram_bot_token: ... ``` -Also: -- Make sure to uncomment `APP_SERVICES_ENABLED` -- include the registration in synapse: `APP_SERVICE_CONFIGS="[\"/telegram-data/registration.yaml\"]"` -- and set yourself as admin under `TELEGRAM_BRIDGE_PERMISSIONS` - A rough guide for the following steps: ``` @@ -122,3 +122,4 @@ OK, it's also awful to set this up. Do you see a pattern emerging :) - deploy the thing and then check the `/data/registration.yaml` - rm the fake `signal_hs/as_token` values and re-insert the new ones from `registration.yaml` - re-deploy the whole thing and then it should come up, message `@signalbot:example.com` to test +- See the [docs](https://docs.mau.fi/bridges/go/signal/authentication.html) for authentication