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`).
14 lines
562 B
YAML
14 lines
562 B
YAML
matrix_postgres_enabled: true
|
|
|
|
matrix_postgres_connection_hostname: ""
|
|
matrix_postgres_connection_username: ""
|
|
matrix_postgres_connection_password: ""
|
|
matrix_postgres_db_name: ""
|
|
|
|
matrix_postgres_base_path: "{{ matrix_base_data_path }}/postgres"
|
|
matrix_postgres_data_path: "{{ matrix_postgres_base_path }}/data"
|
|
|
|
matrix_postgres_docker_image_v9: "postgres:9.6.11-alpine"
|
|
matrix_postgres_docker_image_v10: "postgres:10.6-alpine"
|
|
matrix_postgres_docker_image_v11: "postgres:11.1-alpine"
|
|
matrix_postgres_docker_image_latest: "{{ matrix_postgres_docker_image_v11 }}" |