ansible-collection-famedly-.../roles/synapse/templates/matrix-synapse.service.j2

[Unit]
Description="Matrix Synapse Server (synapse)"
{% if matrix_synapse_workers_enabled | bool %}
{% for worker in matrix_synapse_workers %}
Wants=matrix-{{ worker.name }}.service
{% endfor %}
{% endif %}
After=network.target

[Service]
Type=simple
WorkingDirectory={{ matrix_synapse_base_path }}
ExecStart={{ matrix_synapse_base_path }}/env/bin/python -m synapse.app.homeserver --config-path={{ matrix_synapse_base_path }}/homeserver.yaml
ExecStop={{ matrix_synapse_base_path }}/env/bin/synctl stop {{ matrix_synapse_base_path }}/homeserver.yaml
User=synapse
Group=synapse
Restart=always
StandardOutput=syslog
SyslogIdentifier=matrix_synapse

[Install]
WantedBy=default.target
Template the systemd file 2019-02-21 22:16:22 +00:00			`[Unit]`
			`Description="Matrix Synapse Server (synapse)"`
fix(synapse): allow deploying non-worker systemd setups fixes #9 2021-02-01 21:15:12 +00:00			`{% if matrix_synapse_workers_enabled \| bool %}`
feat(synapse): add support for deploying workers Can deploy synapse workers and allow costum amounts of workers for each type. For documentation on how to use, see `roles/synapse/README.md`. In a docker deployment, each worker runs in their own docker container with respective listener configurations. Labels can be declared in `tasks/configure_workers.yml` for routing of requests. In systemd deployments, each worker runs in it's own systemd service, which are marked as being part of the main service, so restarting the main service will restart all the workers as well. 2020-10-02 07:49:51 +00:00			`{% for worker in matrix_synapse_workers %}`
			`Wants=matrix-{{ worker.name }}.service`
			`{% endfor %}`
fix(synapse): allow deploying non-worker systemd setups fixes #9 2021-02-01 21:15:12 +00:00			`{% endif %}`
feat(synapse): add support for deploying workers Can deploy synapse workers and allow costum amounts of workers for each type. For documentation on how to use, see `roles/synapse/README.md`. In a docker deployment, each worker runs in their own docker container with respective listener configurations. Labels can be declared in `tasks/configure_workers.yml` for routing of requests. In systemd deployments, each worker runs in it's own systemd service, which are marked as being part of the main service, so restarting the main service will restart all the workers as well. 2020-10-02 07:49:51 +00:00			`After=network.target`
Template the systemd file 2019-02-21 22:16:22 +00:00
			`[Service]`
			`Type=simple`
			`WorkingDirectory={{ matrix_synapse_base_path }}`
update synapse to v1.3.0 this includes changes to the logging configuration 2019-08-15 22:41:34 +00:00			`ExecStart={{ matrix_synapse_base_path }}/env/bin/python -m synapse.app.homeserver --config-path={{ matrix_synapse_base_path }}/homeserver.yaml`
Template the systemd file 2019-02-21 22:16:22 +00:00			`ExecStop={{ matrix_synapse_base_path }}/env/bin/synctl stop {{ matrix_synapse_base_path }}/homeserver.yaml`
			`User=synapse`
			`Group=synapse`
			`Restart=always`
			`StandardOutput=syslog`
			`SyslogIdentifier=matrix_synapse`

			`[Install]`
			`WantedBy=default.target`
feat(synapse): add support for deploying workers Can deploy synapse workers and allow costum amounts of workers for each type. For documentation on how to use, see `roles/synapse/README.md`. In a docker deployment, each worker runs in their own docker container with respective listener configurations. Labels can be declared in `tasks/configure_workers.yml` for routing of requests. In systemd deployments, each worker runs in it's own systemd service, which are marked as being part of the main service, so restarting the main service will restart all the workers as well. 2020-10-02 07:49:51 +00:00