c10182e5a6
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`).
18 lines
747 B
YAML
18 lines
747 B
YAML
---
|
|
|
|
- name: Fail if required matrix-corporal settings not defined
|
|
fail:
|
|
msg: >
|
|
You need to define a required configuration setting (`{{ item }}`) for using matrix-corporal.
|
|
when: "vars[item] == ''"
|
|
with_items:
|
|
- "matrix_corporal_matrix_homeserver_api_endpoint"
|
|
- "matrix_corporal_matrix_auth_shared_secret"
|
|
- "matrix_corporal_matrix_registration_shared_secret"
|
|
- "matrix_corporal_policy_provider_config"
|
|
|
|
- name: Fail if HTTP API enabled, but no token set
|
|
fail:
|
|
msg: "The Matrix Corporal HTTP API is enabled (`matrix_corporal_http_api_enabled`), but no auth token has been set in `matrix_corporal_http_api_auth_token`"
|
|
when: "matrix_corporal_http_api_enabled and matrix_corporal_http_api_auth_token == ''"
|