finallycoffee/matrix-docker-ansible-deploy
finallycoffee/matrix-docker-ansible-deploy
5
1
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Enable Telegram self-building

Browse Source
This commit is contained in:
Panagiotis Georgiadis 2021-01-13 16:51:45 +01:00
parent 999fd2596f
commit fd540d8592
No known key found for this signature in database
GPG Key ID: 12E540CAB0E2CCF7
2 changed files with 3 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -12,18 +12,6 @@ matrix_mautrix_telegram_api_id: YOUR_TELEGRAM_APP_ID
matrix_mautrix_telegram_api_hash: YOUR_TELEGRAM_API_HASH
```
**Note**: For architectures different from `amd64` you need to trigger a local rebuild:
```yaml
matrix_mautrix_telegram_container_self_build: true
```
Lastly, to take these changes into effect, re-run the playbook:
```yaml
ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start
```
## Set up Double Puppeting
If you'd like to use [Double Puppeting](https://github.com/tulir/mautrix-telegram/wiki/Authentication#replacing-telegram-accounts-matrix-puppet-with-matrix-account) (hint: you most likely do), you have 2 ways of going about it.

3
group_vars/matrix_servers
View File

@ -305,6 +305,9 @@ matrix_mautrix_signal_database_password: "{{ matrix_synapse_macaroon_secret_key
# We don't enable bridges by default.
matrix_mautrix_telegram_enabled: false
# self-building
matrix_mautrix_telegram_container_self_build: "{{ matrix_architecture != 'amd64'}}"
matrix_mautrix_telegram_systemd_required_services_list: |
{{
['docker.service']