Slavi Pantaleev b222d26c86 Switch to managing cronjobs with the Ansible cron module ... 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)		2019-01-08 12:52:03 +02:00
..
defaults	Switch to managing cronjobs with the Ansible cron module	2019-01-08 12:52:03 +02:00
files/yum.repos.d	Stop using patched synapse_port_db script	2017-10-14 09:58:06 +03:00
tasks	Switch to managing cronjobs with the Ansible cron module	2019-01-08 12:52:03 +02:00
templates	Switch to managing cronjobs with the Ansible cron module	2019-01-08 12:52:03 +02:00