matrix-docker-ansible-deploy/roles/custom/matrix-coturn/templates/systemd/matrix-coturn-reload.service.j2

{#
SPDX-FileCopyrightText: 2021 - 2022 Slavi Pantaleev

SPDX-License-Identifier: AGPL-3.0-or-later
#}

[Unit]
Description=Reloads matrix-coturn so that new SSL certificates can kick in

[Service]
Type=oneshot
ExecStart={{ devture_systemd_docker_base_host_command_systemctl }} reload matrix-coturn.service
Add license information to files for matrix-coturn Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org> 2025-03-01 01:41:49 +09:00			`{#`
			`SPDX-FileCopyrightText: 2021 - 2022 Slavi Pantaleev`

			`SPDX-License-Identifier: AGPL-3.0-or-later`
			`#}`

Replace cronjobs with systemd timers Fixes https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/756 Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/737 I feel like timers are somewhat more complicated and dirty (compared to cronjobs), but they come with these benefits: - log output goes to journald - on newer systemd distros, you can see when the timer fired, when it will fire, etc. - we don't need to rely on cron (reducing our dependencies to just systemd + Docker) Cronjobs work well, but it's one more dependency that needs to be installed. We were even asking people to install it manually (in `docs/prerequisites.md`), which could have gone unnoticed. Once in a while someone says "my SSL certificates didn't renew" and it's likely because they forgot to install a cron daemon. Switching to systemd timers means that installation is simpler and more unified. 2021-01-14 23:23:46 +02:00			`[Unit]`
			`Description=Reloads matrix-coturn so that new SSL certificates can kick in`

			`[Service]`
			`Type=oneshot`
matrix_host_command_systemctl -> devture_systemd_docker_base_host_command_systemctl (via com.devture.ansible.role.systemd_docker_base) 2022-11-04 16:41:23 +02:00			`ExecStart={{ devture_systemd_docker_base_host_command_systemctl }} reload matrix-coturn.service`