mirror of
https://github.com/spantaleev/matrix-docker-ansible-deploy.git
synced 2024-12-22 04:34:00 +00:00
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.
19 lines
818 B
YAML
19 lines
818 B
YAML
---
|
|
|
|
# Tells whether this role had executed or not. Toggled to `true` during runtime.
|
|
matrix_nginx_proxy_role_executed: false
|
|
|
|
matrix_ssl_renewal_systemd_units_list:
|
|
- name: matrix-ssl-lets-encrypt-certificates-renew.service
|
|
applicable: "{{ matrix_ssl_retrieval_method == 'lets-encrypt' }}"
|
|
enableable: false
|
|
- name: matrix-ssl-lets-encrypt-certificates-renew.timer
|
|
applicable: "{{ matrix_ssl_retrieval_method == 'lets-encrypt' }}"
|
|
enableable: true
|
|
- name: matrix-ssl-nginx-proxy-reload.service
|
|
applicable: "{{ matrix_ssl_retrieval_method == 'lets-encrypt' and matrix_nginx_proxy_enabled|bool }}"
|
|
enableable: false
|
|
- name: matrix-ssl-nginx-proxy-reload.timer
|
|
applicable: "{{ matrix_ssl_retrieval_method == 'lets-encrypt' and matrix_nginx_proxy_enabled|bool }}"
|
|
enableable: true
|