titanz
/
matrix-docker-ansible-deploy
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'de378c6390'
${ noResults }
matrix-docker-ansible-deploy/roles/matrix-bridge-mautrix-whatsapp/tasks/setup_uninstall.yml

26 lines
798 B
Raw Normal View History Unescape

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).
6 years ago
---
Make bridge uninstallation stop services Fixes #155 (Github Issue)
6 years ago
- name: Check existence of matrix-mautrix-whatsapp service
stat:
Made directory variables for /etc/systemd/system , /etc/cron.d , /usr/local/bin
5 years ago
path: "{{ matrix_systemd_path }}/matrix-mautrix-whatsapp.service"
Make bridge uninstallation stop services Fixes #155 (Github Issue)
6 years ago
register: matrix_mautrix_whatsapp_service_stat
- name: Ensure matrix-mautrix-whatsapp is stopped
service:
name: matrix-mautrix-whatsapp
state: stopped
fix: all praise the allmighty yamllinter
3 years ago
enabled: false
daemon_reload: true
Make bridge uninstallation stop services Fixes #155 (Github Issue)
6 years ago
when: "matrix_mautrix_whatsapp_service_stat.stat.exists"
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).
6 years ago
- name: Ensure matrix-mautrix-whatsapp.service doesn't exist
file:
Made directory variables for /etc/systemd/system , /etc/cron.d , /usr/local/bin
5 years ago
path: "{{ matrix_systemd_path }}/matrix-mautrix-whatsapp.service"
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).
6 years ago
state: absent
Make bridge uninstallation stop services Fixes #155 (Github Issue)
6 years ago
when: "matrix_mautrix_whatsapp_service_stat.stat.exists"
- name: Ensure systemd reloaded after matrix-mautrix-whatsapp.service removal
service:
fix: all praise the allmighty yamllinter
3 years ago
daemon_reload: true
Make bridge uninstallation stop services Fixes #155 (Github Issue)
6 years ago
when: "matrix_mautrix_whatsapp_service_stat.stat.exists"