matrix-docker-ansible-deploy/roles/matrix-nginx-proxy/tasks/init.yml

- set_fact:
    matrix_systemd_services_list: "{{ matrix_systemd_services_list + ['matrix-nginx-proxy.service'] }}"
  when: matrix_nginx_proxy_enabled|bool

- set_fact:
    matrix_systemd_services_list: "{{ matrix_systemd_services_list + [item.name] }}"
  when: "item.applicable|bool and item.enableable|bool"
  with_items: "{{ matrix_ssl_renewal_systemd_units_list }}"
Split playbook into multiple roles As suggested in #63 (Github issue), splitting the playbook's logic into multiple roles will be beneficial for maintainability. This patch realizes this split. Still, some components affect others, so the roles are not really independent of one another. For example: - disabling mxisd (`matrix_mxisd_enabled: false`), causes Synapse and riot-web to reconfigure themselves with other (public) Identity servers. - enabling matrix-corporal (`matrix_corporal_enabled: true`) affects how reverse-proxying (by `matrix-nginx-proxy`) is done, in order to put matrix-corporal's gateway server in front of Synapse We may be able to move away from such dependencies in the future, at the expense of a more complicated manual configuration, but it's probably not worth sacrificing the convenience we have now. As part of this work, the way we do "start components" has been redone now to use a loop, as suggested in #65 (Github issue). This should make restarting faster and more reliable. 2019-01-12 15:53:00 +00:00			`- set_fact:`
Add .service suffix to systemd units list We'll be adding `.timer` units later on, so it's good to be more explicit. 2021-01-14 21:02:10 +00:00			`matrix_systemd_services_list: "{{ matrix_systemd_services_list + ['matrix-nginx-proxy.service'] }}"`
Fix CONDITIONAL_BARE_VARS deprecation warning in ansible 2.8 2019-05-21 15:25:59 +00:00			`when: matrix_nginx_proxy_enabled\|bool`
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
			`- set_fact:`
			`matrix_systemd_services_list: "{{ matrix_systemd_services_list + [item.name] }}"`
			`when: "item.applicable\|bool and item.enableable\|bool"`
			`with_items: "{{ matrix_ssl_renewal_systemd_units_list }}"`