bb816df557
The goal is to move each bridge into its own separate role. This commit starts off the work on this with 2 bridges: - mautrix-telegram - mautrix-whatsapp Each bridge's role (including these 2) is meant to: - depend only on the matrix-base role - integrate nicely with the matrix-synapse role (if available) - integrate nicely with the matrix-nginx-proxy role (if available and if required). mautrix-telegram bridge benefits from integrating with it. - not break if matrix-synapse or matrix-nginx-proxy are not used at all This has been provoked by #174 (Github Issue).
12 lines
314 B
YAML
12 lines
314 B
YAML
---
|
|
|
|
- name: Fail if required settings not defined
|
|
fail:
|
|
msg: >-
|
|
You need to define a required configuration setting (`{{ item }}`).
|
|
when: "vars[item] == ''"
|
|
with_items:
|
|
- "matrix_mautrix_telegram_api_id"
|
|
- "matrix_mautrix_telegram_api_hash"
|
|
- "matrix_mautrix_telegram_public_endpoint"
|