e1690722f7
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. |
||
---|---|---|
.. | ||
matrix-aux | ||
matrix-base | ||
matrix-bot-matrix-reminder-bot | ||
matrix-bridge-appservice-discord | ||
matrix-bridge-appservice-irc | ||
matrix-bridge-appservice-slack | ||
matrix-bridge-appservice-webhooks | ||
matrix-bridge-mautrix-facebook | ||
matrix-bridge-mautrix-hangouts | ||
matrix-bridge-mautrix-signal | ||
matrix-bridge-mautrix-telegram | ||
matrix-bridge-mautrix-whatsapp | ||
matrix-bridge-mx-puppet-discord | ||
matrix-bridge-mx-puppet-instagram | ||
matrix-bridge-mx-puppet-skype | ||
matrix-bridge-mx-puppet-slack | ||
matrix-bridge-mx-puppet-steam | ||
matrix-bridge-mx-puppet-twitter | ||
matrix-bridge-sms | ||
matrix-client-element | ||
matrix-common-after/tasks | ||
matrix-corporal | ||
matrix-coturn | ||
matrix-dimension | ||
matrix-dynamic-dns | ||
matrix-email2matrix | ||
matrix-jitsi | ||
matrix-ma1sd | ||
matrix-mailer | ||
matrix-nginx-proxy | ||
matrix-postgres | ||
matrix-registration | ||
matrix-synapse | ||
matrix-synapse-admin |