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).
7 lines
156 B
YAML
7 lines
156 B
YAML
---
|
|
|
|
- name: Ensure matrix-mautrix-telegram.service doesn't exist
|
|
file:
|
|
path: "/etc/systemd/system/matrix-mautrix-telegram.service"
|
|
state: absent
|