matrix-docker-ansible-deploy/roles/matrix-jitsi/templates/prosody/matrix-jitsi-prosody.servic...

#jinja2: lstrip_blocks: "True"
[Unit]
Description=Matrix jitsi-prosody server
{% for service in matrix_jitsi_prosody_systemd_required_services_list %}
Requires={{ service }}
After={{ service }}
{% endfor %}
DefaultDependencies=no

[Service]
Type=simple
ExecStartPre=-{{ matrix_host_command_docker }} kill matrix-jitsi-prosody
ExecStartPre=-{{ matrix_host_command_docker }} rm matrix-jitsi-prosody

ExecStart={{ matrix_host_command_docker }} run --rm --name matrix-jitsi-prosody \
			--log-driver=none \
			--network={{ matrix_docker_network }} \
			--env-file={{ matrix_jitsi_prosody_base_path }}/env \
			--mount type=bind,src={{ matrix_jitsi_prosody_config_path }},dst=/config \
			--mount type=bind,src={{ matrix_jitsi_prosody_plugins_path }},dst=/prosody-plugins-custom \
			{% for arg in matrix_jitsi_prosody_container_extra_arguments %}
			{{ arg }} \
			{% endfor %}
			{{ matrix_jitsi_prosody_docker_image }}

ExecStop=-{{ matrix_host_command_docker }} kill matrix-jitsi-prosody
ExecStop=-{{ matrix_host_command_docker }} rm matrix-jitsi-prosody
Restart=always
RestartSec=30
SyslogIdentifier=matrix-jitsi-prosody

[Install]
WantedBy=multi-user.target
Add Jitsi support 5 years ago			`#jinja2: lstrip_blocks: "True"`
			`[Unit]`
			`Description=Matrix jitsi-prosody server`
			`{% for service in matrix_jitsi_prosody_systemd_required_services_list %}`
			`Requires={{ service }}`
			`After={{ service }}`
			`{% endfor %}`
Fix systemd services autostart problem with Docker 20.10 The Docker 19.04 -> 20.10 upgrade contains the following change in `/usr/lib/systemd/system/docker.service`: ``` -BindsTo=containerd.service -After=network-online.target firewalld.service containerd.service +After=network-online.target firewalld.service containerd.service multi-user.target -Requires=docker.socket +Requires=docker.socket containerd.service Wants=network-online.target ``` The `multi-user.target` requirement in `After` seems to be in conflict with our `WantedBy=multi-user.target` and `After=docker.service` / `Requires=docker.service` definitions, causing the following error on startup for all of our systemd services: > Job matrix-synapse.service/start deleted to break ordering cycle starting with multi-user.target/start A workaround which appears to work is to add `DefaultDependencies=no` to all of our services. 4 years ago			`DefaultDependencies=no`
Add Jitsi support 5 years ago
			`[Service]`
			`Type=simple`
Remove hardcoded command paths in systemd unit files Depending on the distro, common commands like sleep and chown may either be located in /bin or /usr/bin. Systemd added path lookup to ExecStart in v239, allowing only the command name to be put in unit files and not the full path as historically required. At least Ubuntu 18.04 LTS is however still on v237 so we should maintain portability for a while longer. 5 years ago			`ExecStartPre=-{{ matrix_host_command_docker }} kill matrix-jitsi-prosody`
			`ExecStartPre=-{{ matrix_host_command_docker }} rm matrix-jitsi-prosody`
Add Jitsi support 5 years ago
Remove hardcoded command paths in systemd unit files Depending on the distro, common commands like sleep and chown may either be located in /bin or /usr/bin. Systemd added path lookup to ExecStart in v239, allowing only the command name to be put in unit files and not the full path as historically required. At least Ubuntu 18.04 LTS is however still on v237 so we should maintain portability for a while longer. 5 years ago			`ExecStart={{ matrix_host_command_docker }} run --rm --name matrix-jitsi-prosody \`
Add Jitsi support 5 years ago			`--log-driver=none \`
			`--network={{ matrix_docker_network }} \`
			`--env-file={{ matrix_jitsi_prosody_base_path }}/env \`
Replace some -v instances with --mount `-v` magically creates the source destination as a directory, if it doesn't exist already. We'd like to avoid this magic and the potential breakage that it might cause. We'd rather fail while Docker tries to find things to `--mount` than have it automatically create directories and fail anyway, while having contaminated the filesystem. There's a lot more `-v` instances remaining to be fixed later on. This is just some start. Things like `matrix_synapse_container_additional_volumes` and `matrix_nginx_proxy_container_additional_volumes` were not changed to use `--mount`, as options for each one are passed differently (`ro` is `ro`, but `rw` doesn't exist and `slave` is `bind-propagation=slave`). To avoid breaking people's custom volume mounts, we keep it as it is for now. A deficiency with `--mount` is that it lacks the `z` option (SELinux ownership changes), and some of our `-v` instances use that. I'm not sure how supported SELinux is for us right now, but it might be, and breaking that would not be a good idea. 4 years ago			`--mount type=bind,src={{ matrix_jitsi_prosody_config_path }},dst=/config \`
			`--mount type=bind,src={{ matrix_jitsi_prosody_plugins_path }},dst=/prosody-plugins-custom \`
Add Jitsi support 5 years ago			`{% for arg in matrix_jitsi_prosody_container_extra_arguments %}`
			`{{ arg }} \`
			`{% endfor %}`
			`{{ matrix_jitsi_prosody_docker_image }}`

Remove hardcoded command paths in systemd unit files Depending on the distro, common commands like sleep and chown may either be located in /bin or /usr/bin. Systemd added path lookup to ExecStart in v239, allowing only the command name to be put in unit files and not the full path as historically required. At least Ubuntu 18.04 LTS is however still on v237 so we should maintain portability for a while longer. 5 years ago			`ExecStop=-{{ matrix_host_command_docker }} kill matrix-jitsi-prosody`
			`ExecStop=-{{ matrix_host_command_docker }} rm matrix-jitsi-prosody`
Add Jitsi support 5 years ago			`Restart=always`
			`RestartSec=30`
			`SyslogIdentifier=matrix-jitsi-prosody`

			`[Install]`
			`WantedBy=multi-user.target`