matrix-docker-ansible-deploy/roles/matrix-synapse/tasks
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
..
ext Move mautrix telegram and whatsapp into separate roles 2019-05-14 23:47:22 +09:00
import_media_store.yml
init.yml
main.yml Move mautrix telegram and whatsapp into separate roles 2019-05-14 23:47:22 +09:00
register_user.yml
self_check_client_api.yml
self_check_federation_api.yml
setup_synapse_entrypoint.yml
setup_synapse_goofys.yml
setup_synapse_main.yml Use the '-p' non-interactive option to generate password hash instead of 'expect' 2019-05-03 11:02:17 +03:00
setup_synapse_pre.yml
update_user_password.yml Use the '-p' non-interactive option to generate password hash instead of 'expect' 2019-05-03 11:02:17 +03:00
validate_config.yml