matrix-docker-ansible-deploy/roles/matrix-base/tasks
Slavi Pantaleev c10182e5a6 Make roles more independent of one another
With this change, the following roles are now only dependent
on the minimal `matrix-base` role:
- `matrix-corporal`
- `matrix-coturn`
- `matrix-mailer`
- `matrix-mxisd`
- `matrix-postgres`
- `matrix-riot-web`
- `matrix-synapse`

The `matrix-nginx-proxy` role still does too much and remains
dependent on the others.

Wiring up the various (now-independent) roles happens
via a glue variables file (`group_vars/matrix-servers`).
It's triggered for all hosts in the `matrix-servers` group.

According to Ansible's rules of priority, we have the following
chain of inclusion/overriding now:
- role defaults (mostly empty or good for independent usage)
- playbook glue variables (`group_vars/matrix-servers`)
- inventory host variables (`inventory/host_vars/matrix.<your-domain>`)

All roles default to enabling their main component
(e.g. `matrix_mxisd_enabled: true`, `matrix_riot_web_enabled: true`).
Reasoning: if a role is included in a playbook (especially separately,
in another playbook), it should "work" by default.

Our playbook disables some of those if they are not generally useful
(e.g. `matrix_corporal_enabled: false`).
2019-01-16 18:05:48 +02:00
..
clean_up_old_files.yml Split playbook into multiple roles 2019-01-12 18:01:10 +02:00
main.yml Split playbook into multiple roles 2019-01-12 18:01:10 +02:00
sanity_check.yml Make roles more independent of one another 2019-01-16 18:05:48 +02:00
self_check_dns.yml Split playbook into multiple roles 2019-01-12 18:01:10 +02:00
self_check_dns_srv.yml Split playbook into multiple roles 2019-01-12 18:01:10 +02:00
setup_matrix_base.yml Make the mode of the base path configurable 2019-01-14 14:40:11 +00:00
setup_server_base.yml Split playbook into multiple roles 2019-01-12 18:01:10 +02:00
setup_well_known.yml Split playbook into multiple roles 2019-01-12 18:01:10 +02:00