From 72b59ce4ad44c3d872da013b90851822b5a96531 Mon Sep 17 00:00:00 2001 From: Simon Date: Wed, 13 Mar 2024 14:18:51 +0100 Subject: [PATCH] chore: publish 5.0.4+v1.100.0 release --- .env.sample | 6 +++--- README.md | 9 +++++++-- 2 files changed, 10 insertions(+), 5 deletions(-) diff --git a/.env.sample b/.env.sample index acb4109..27c6e5d 100644 --- a/.env.sample +++ b/.env.sample @@ -132,12 +132,12 @@ RETENTION_MAX_LIFETIME=4w #APP_SERVICE_BOT_USERNAME=telegrambot #APP_SERVICE_DISPLAY_NAME="Telegram bridge bot" #APP_SERVICE_ID= -#HOMESERVER_DOMAIN= -#HOMESERVER_URL= +#HOMESERVER_DOMAIN=$DOMAIN +#HOMESERVER_URL=https://$DOMAIN #VERIFY_SSL=false #ENABLE_ENCRYPTION=true #TELEGRAM_APP_ID= -#TELEGRAM_BRIDGE_PERMISSIONS="{ \"*\": \"relaybot\" }" +#TELEGRAM_BRIDGE_PERMISSIONS="{ \"*\": \"relaybot\", \"@foo:matrix.example.com\": \"admin\" }" #TELEGRAM_SYNC_CHANNEL_MEMBERS=true #SECRET_TELEGRAM_DB_PASSWORD_VERSION=v1 #SECRET_TELEGRAM_API_HASH_VERSION=v1 diff --git a/README.md b/README.md index 8c7aba6..f07a3d6 100644 --- a/README.md +++ b/README.md @@ -47,7 +47,7 @@ You'll need to deploy something like [this](https://git.autonomic.zone/ruangrupa 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 and have these values: +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: ``` api_id: ... @@ -55,7 +55,12 @@ api_hash: ... telegram_bot_token: ... ``` -Here is a rough guide: +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: ``` abra app secret insert telegram_api_hash v1