mirror/matrix-docker-ansible-deploy
1
0
Fork 0
mirror of https://github.com/spantaleev/matrix-docker-ansible-deploy.git synced 2024-11-06 18:57:37 +01:00
Code Issues Packages Projects Releases Wiki Activity
8c2b77bf0c
matrix-docker-ansible-deploy/roles/custom/matrix-bridge-mautrix-whatsapp/tasks/main.yml

30 lines
871 B
YAML
Raw Normal View History

fix: all praise the allmighty yamllinter
2022-02-05 21:32:54 +01:00
---
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 16:47:22 +02:00
add nginx proxy connfig for mautrix metrics
2023-01-29 15:13:42 +01:00
- block:
- when: matrix_mautrix_whatsapp_enabled | bool and matrix_mautrix_whatsapp_metrics_enabled | bool
ansible.builtin.include_tasks: "{{ role_path }}/tasks/inject_into_nginx_proxy.yml"
tags:
- setup-all
- setup-nginx-proxy
- install-all
- install-nginx-proxy
Replace most import_tasks calls with include_tasks for improved performance
2022-11-24 10:33:30 +01:00
- block:
- when: matrix_mautrix_whatsapp_enabled | bool
ansible.builtin.include_tasks: "{{ role_path }}/tasks/validate_config.yml"
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
Replace most import_tasks calls with include_tasks for improved performance
2022-11-24 10:33:30 +01:00
- when: matrix_mautrix_whatsapp_enabled | bool
ansible.builtin.include_tasks: "{{ role_path }}/tasks/setup_install.yml"
Add install-* tags for quicker runs
2022-11-25 15:02:51 +01:00
tags:
- setup-all
- setup-mautrix-whatsapp
- install-all
- install-mautrix-whatsapp
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 16:47:22 +02:00
Add install-* tags for quicker runs
2022-11-25 15:02:51 +01:00
- block:
Replace most import_tasks calls with include_tasks for improved performance
2022-11-24 10:33:30 +01:00
- when: not matrix_mautrix_whatsapp_enabled | bool
ansible.builtin.include_tasks: "{{ role_path }}/tasks/setup_uninstall.yml"
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 16:47:22 +02:00
tags:
- setup-all
- setup-mautrix-whatsapp
Reference in New Issue Copy Permalink