docs

examples

group_vars

inventory

roles

matrix-base

matrix-bridge-appservice-discord

matrix-bridge-appservice-irc

matrix-bridge-mautrix-facebook

matrix-bridge-mautrix-hangouts

matrix-bridge-mautrix-telegram

matrix-bridge-mautrix-whatsapp

matrix-common-after

matrix-corporal

matrix-coturn

matrix-dimension

matrix-mailer

matrix-mxisd

matrix-nginx-proxy

matrix-postgres

matrix-riot-web

matrix-synapse

defaults

tasks

templates

vars

main.yml

.editorconfig

.gitignore

CHANGELOG.md

LICENSE

README.md

ansible.cfg

setup.yml

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

..

main.yml

Move mautrix telegram and whatsapp into separate roles

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