matrix-docker-ansible-deploy/roles/matrix-synapse/tasks/ext
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
..
appservice-discord Skip some tasks when not necessary to run them 2019-03-08 12:14:58 +02:00
appservice-irc Start appservice-irc as non-root 2019-03-12 13:17:51 -04:00
ldap-auth Split playbook into multiple roles 2019-01-12 18:01:10 +02:00
mautrix-facebook Add tulir mautrix-facebook (https://github.com/tulir/mautrix-facebook) 2019-05-08 17:11:07 +02:00
rest-auth Split playbook into multiple roles 2019-01-12 18:01:10 +02:00
shared-secret-auth Split playbook into multiple roles 2019-01-12 18:01:10 +02:00
init.yml Move mautrix telegram and whatsapp into separate roles 2019-05-14 23:47:22 +09:00
setup.yml Move mautrix telegram and whatsapp into separate roles 2019-05-14 23:47:22 +09:00