bb816df557
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).
37 lines
1.1 KiB
Django/Jinja
37 lines
1.1 KiB
Django/Jinja
#jinja2: lstrip_blocks: "True"
|
|
[Unit]
|
|
Description=Matrix Mautrix Whatsapp server
|
|
{% 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 %}
|
|
|
|
[Service]
|
|
Type=simple
|
|
ExecStartPre=-/usr/bin/docker kill matrix-mautrix-whatsapp
|
|
ExecStartPre=-/usr/bin/docker rm matrix-mautrix-whatsapp
|
|
|
|
ExecStart=/usr/bin/docker run --rm --name matrix-mautrix-whatsapp \
|
|
--log-driver=none \
|
|
--user={{ matrix_user_uid }}:{{ matrix_user_gid }} \
|
|
--cap-drop=ALL \
|
|
--network={{ matrix_docker_network }} \
|
|
-v {{ matrix_mautrix_whatsapp_base_path }}:/data:z \
|
|
--workdir=/data \
|
|
{% for arg in matrix_mautrix_whatsapp_container_extra_arguments %}
|
|
{{ arg }} \
|
|
{% endfor %}
|
|
{{ matrix_mautrix_whatsapp_docker_image }} \
|
|
/usr/bin/mautrix-whatsapp
|
|
|
|
ExecStop=-/usr/bin/docker kill matrix-mautrix-whatsapp
|
|
ExecStop=-/usr/bin/docker rm matrix-mautrix-whatsapp
|
|
Restart=always
|
|
RestartSec=30
|
|
|
|
[Install]
|
|
WantedBy=multi-user.target
|