matrix-docker-ansible-deploy/setup-uninstall.yml at bb816df557c5040fbc59a7935e407df1df677e89 - matrix-docker-ansible-deploy - awful git

jowj/matrix-docker-ansible-deploy

forked from mirrors/matrix-docker-ansible-deploy

Slavi Pantaleev bb816df557 Move mautrix telegram and whatsapp into separate roles

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).

2019-05-14 23:47:22 +09:00

7 lines

156 B

YAML

Raw Blame History

 ---
 - name: Ensure matrix-mautrix-whatsapp.service doesn't exist
   file:
     path: "/etc/systemd/system/matrix-mautrix-whatsapp.service"
     state: absent