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

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

[Timer]
Unit=matrix-coturn-reload.service
OnCalendar={{ matrix_coturn_reload_schedule }}
RandomizedDelaySec={{ matrix_coturn_reload_schedule_randomized_delay_sec }}

[Install]
WantedBy=timers.target
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 21:23:46 +00:00			`[Unit]`
			`Description=Reloads matrix-coturn periodically so that new SSL certificates can kick in`

			`[Timer]`
			`Unit=matrix-coturn-reload.service`
Update files for matrix-coturn: make the reloading schedule configurable with variables This commit adopts the common format which can be seen for BorgBackup. It should be probably helpful, though I am not quite sure how much. Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org> 2025-02-01 06:34:46 +00:00			`OnCalendar={{ matrix_coturn_reload_schedule }}`
			`RandomizedDelaySec={{ matrix_coturn_reload_schedule_randomized_delay_sec }}`
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 21:23:46 +00:00
			`[Install]`
			`WantedBy=timers.target`