ansol/matrix-docker-ansible-deploy
7
0
Fork 0
mirror of https://github.com/spantaleev/matrix-docker-ansible-deploy.git synced 2024-12-22 20:45:48 +00:00
Code Issues Projects Releases Wiki Activity

Merge pull request #318 from benkuly/master

Browse Source 
Add telegram relay bot feature to playbook
This commit is contained in:
Slavi Pantaleev 2019-12-03 12:02:46 +02:00 committed by GitHub
commit 163a1b4294
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 8 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/configuring-playbook-bridge-mautrix-telegram.md
View File

@ -13,3 +13,9 @@ matrix_mautrix_telegram_api_hash: YOUR_TELEGRAM_API_HASH
```
You then need to start a chat with `@telegrambot:YOUR_DOMAIN` (where `YOUR_DOMAIN` is your base domain, not the `matrix.` domain).
If you want to use the relay-bot feature ([relay bot documentation](https://github.com/tulir/mautrix-telegram/wiki/Relay-bot)), which allows anonymous user to chat with telegram users, use the following additional playbook configuration:
```yaml
matrix_mautrix_telegram_bot_token: YOUT_TELEGRAM_BOT_TOKEN
```

3
roles/matrix-bridge-mautrix-telegram/defaults/main.yml
View File

@ -14,6 +14,7 @@ matrix_mautrix_telegram_data_path: "{{ matrix_mautrix_telegram_base_path }}/data
# Get your own API keys at https://my.telegram.org/apps
matrix_mautrix_telegram_api_id: ''
matrix_mautrix_telegram_api_hash: ''
matrix_mautrix_telegram_bot_token: disabled
# Mautrix telegram public endpoint to log in to telegram
# Use an uuid so it's not easily discoverable.
@ -297,7 +298,7 @@ matrix_mautrix_telegram_configuration_yaml: |
api_id: {{ matrix_mautrix_telegram_api_id }}
api_hash: {{ matrix_mautrix_telegram_api_hash }}
# (Optional) Create your own bot at https://t.me/BotFather
bot_token: disabled
bot_token: {{ matrix_mautrix_telegram_bot_token }}
# Telethon connection options.
connection: