pub-solar/matrix-docker-ansible-deploy
5
0
Fork 0
Code Issues Pull requests Packages Projects Releases Wiki Activity
1570 commits 2 branches 0 tags 16 MiB
Commit graph

6 commits

Author SHA1 Message Date
Mike 4edb1eb131
Update init.yml 
Removed a set_facts that I have used for tracing down the issue
 2019-11-09 23:53:04 +01:00
Michael Haak 5b213e6ad0 Replace constructs appending elements with variables to matrix_synapse_container_extra_arguments. Fixes issue https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/304 2019-11-09 23:16:12 +01:00
Thomas Kuehne 4797469383 Make WhatsApp bridge configuration playbook-managed 
- following spantaleev transition of the telegram brigde
- adding a validate_config task
 2019-06-24 00:16:04 +02:00
Slavi Pantaleev 00383a73ac Make running --tags=setup-synapse only not fail to register bridges 
Until now, if `--tags=setup-synapse` was used, bridge tasks would not
run and bridges would fail to register with the `matrix-synapse` role.
This means that Synapse's configuration would be generated with an empty
list of appservices (`app_service_config_files: []`).

.. and then bridges would fail, because Synapse would not be aware of
there being any bridges.

From now on, bridges always run their init tasks and always register
with Synapse.

For the Telegram bridge, the same applies to registering with
matrix-nginx-proxy. Previously, running `--tags=setup-nginx-proxy` would
get rid of the Telegram endpoint configuration for the same reason.
Not anymore.
 2019-06-14 10:19:52 +03:00
Dan Arnfield 3982f114af Fix CONDITIONAL_BARE_VARS deprecation warning in ansible 2.8 2019-05-21 10:25:59 -05:00
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
Renamed from roles/matrix-synapse/tasks/ext/mautrix-whatsapp/init.yml (Browse further)