docs
examples
inventory
roles
matrix-server
defaults
files
tasks
import
self_check
setup
ssl
main.yml
setup_ssl_lets_encrypt.yml
setup_ssl_lets_encrypt_obtain_for_domain.yml
setup_ssl_manually_managed.yml
setup_ssl_manually_managed_verify_for_domain.yml
setup_ssl_self_signed.yml
setup_ssl_self_signed_obtain_for_domain.yml
synapse
main.yml
setup_base.yml
setup_corporal.yml
setup_corporal_overrides.yml
setup_coturn.yml
setup_goofys.yml
setup_mailer.yml
setup_main.yml
setup_mxisd.yml
setup_nginx_proxy.yml
setup_postgres.yml
setup_riot_web.yml
setup_sanity_check.yml
setup_well_known.yml
util
main.yml
register_user.yml
start.yml
upgrade_postgres.yml
templates
.gitignore
CHANGELOG.md
LICENSE
README.md
ansible.cfg
setup.yml
b222d26c86
As suggested in #65 (Github issue), this patch switches cronjob management from using templates to using Ansible's `cron` module. It also moves the management of the nginx-reload cronjob to `setup_ssl_lets_encrypt.yml`, which is a more fitting place for it (given that this cronjob is only required when Let's Encrypt is used). Pros: - using a module is more Ansible-ish than templating our own files in special directories - more reliable: will fail early (during playbook execution) if `/usr/bin/crontab` is not available, which is more of a guarantee that cron is working fine (idea: we should probably install some cron package using the playbook) Cons: - invocation schedule is no longer configurable, unless we define individual variables for everything or do something smart (splitting on ' ', etc.). Likely not necessary, however. - requires us to deprecate and clean-up after the old way of managing cronjobs, because it's not compatible (using the same file as before means appending additional jobs to it)