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).
20 lines
441 B
YAML
Executable file
20 lines
441 B
YAML
Executable file
---
|
|
- name: "Set up a Matrix server"
|
|
hosts: "{{ target if target is defined else 'matrix-servers' }}"
|
|
become: true
|
|
|
|
roles:
|
|
- matrix-base
|
|
- matrix-mailer
|
|
- matrix-postgres
|
|
- matrix-corporal
|
|
- matrix-bridge-mautrix-telegram
|
|
- matrix-bridge-mautrix-whatsapp
|
|
- matrix-synapse
|
|
- matrix-riot-web
|
|
- matrix-mxisd
|
|
- matrix-dimension
|
|
- matrix-nginx-proxy
|
|
- matrix-coturn
|
|
- matrix-common-after
|