pub-solar/matrix-docker-ansible-deploy
5
0
Fork 0
Code Issues Pull requests Packages Projects Releases Wiki Activity
matrix-docker-ansible-deploy/roles/matrix-bridge-mautrix-whatsapp/templates/systemd/matrix-mautrix-whatsapp.service.j2

42 lines
1.3 KiB
Plaintext
Raw Normal View History

Fix indentation in templates Use Jinja2 lstrip_blocks option in templates to ensure consistent indentation in generated files.
2019-05-07 19:23:35 +00:00
#jinja2: lstrip_blocks: "True"
Add mautrix-whatsapp
2018-10-24 13:18:55 +00:00
[Unit]
Description=Matrix Mautrix Whatsapp server
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 14:47:22 +00:00
{% for service in matrix_mautrix_whatsapp_systemd_required_services_list %}
Requires={{ service }}
After={{ service }}
{% endfor %}
{% for service in matrix_mautrix_whatsapp_systemd_wanted_services_list %}
Wants={{ service }}
{% endfor %}
Add mautrix-whatsapp
2018-10-24 13:18:55 +00:00
[Service]
Type=simple
ExecStartPre=-/usr/bin/docker kill matrix-mautrix-whatsapp
ExecStartPre=-/usr/bin/docker rm matrix-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 14:47:22 +00:00
Delay bridge startup to ensure Synapse is up Bridges start matrix-synapse.service as a dependency, but Synapse is sometimes slow to start, while bridges are quick to hit it and die (if unavailable). They'll auto-restart later, but .. this still breaks `--tags=start`, which doesn't wait long enough for such a restart to happen. This attempts to slow down bridge startup enough to ensure Synapse is up and no failures happen at all.
2019-06-07 09:15:37 +00:00
# Intentional delay, so that the homeserver (we likely depend on) can manage to start.
ExecStartPre=/bin/sleep 5
Add mautrix-whatsapp
2018-10-24 13:18:55 +00:00
ExecStart=/usr/bin/docker run --rm --name matrix-mautrix-whatsapp \
--log-driver=none \
Make mautrix-whatsapp run as non-root and w/o capabilities
2019-01-28 13:55:58 +00:00
--user={{ matrix_user_uid }}:{{ matrix_user_gid }} \
--cap-drop=ALL \
Add mautrix-whatsapp
2018-10-24 13:18:55 +00:00
--network={{ matrix_docker_network }} \
Make WhatsApp bridge configuration playbook-managed - following spantaleev transition of the telegram brigde - adding a validate_config task
2019-06-23 22:16:04 +00:00
-v {{ matrix_mautrix_whatsapp_config_path }}:/config:z \
Fix indentation consistency
2019-06-24 04:42:39 +00:00
-v {{ matrix_mautrix_whatsapp_data_path }}:/data:z \
Make mautrix-whatsapp run as non-root and w/o capabilities
2019-01-28 13:55:58 +00:00
--workdir=/data \
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 14:47:22 +00:00
{% for arg in matrix_mautrix_whatsapp_container_extra_arguments %}
{{ arg }} \
{% endfor %}
Make mautrix-whatsapp run as non-root and w/o capabilities
2019-01-28 13:55:58 +00:00
{{ matrix_mautrix_whatsapp_docker_image }} \
Make WhatsApp bridge configuration playbook-managed - following spantaleev transition of the telegram brigde - adding a validate_config task
2019-06-23 22:16:04 +00:00
/usr/bin/mautrix-whatsapp -c /config/config.yaml -r /config/registration.yaml
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 14:47:22 +00:00
Add mautrix-whatsapp
2018-10-24 13:18:55 +00:00
ExecStop=-/usr/bin/docker kill matrix-mautrix-whatsapp
ExecStop=-/usr/bin/docker rm matrix-mautrix-whatsapp
Restart=always
RestartSec=30
Use SyslogIdentifier to improve logging Reasoning is the same as for matrix-org/synapse#5023. For us, the journal used to contain `docker` for all services, which is not very helpful when looking at them all together (`journalctl -f`).
2019-05-16 00:41:45 +00:00
SyslogIdentifier=matrix-mautrix-whatsapp
Add mautrix-whatsapp
2018-10-24 13:18:55 +00:00
[Install]
WantedBy=multi-user.target
Reference in a new issue Copy permalink