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`).
22 lines
1.5 KiB
Markdown
22 lines
1.5 KiB
Markdown
# Using an external PostgreSQL server (optional)
|
|
|
|
By default, this playbook would set up a PostgreSQL database server on your machine, running in a Docker container.
|
|
If that's alright, you can skip this.
|
|
|
|
If you'd like to use an external PostgreSQL server that you manage, you can edit your configuration file (`inventory/matrix.<your-domain>/vars.yml`).
|
|
It should be something like this:
|
|
|
|
```yaml
|
|
matrix_postgres_enabled: false
|
|
|
|
# Rewire Synapse to use your external Postgres server
|
|
matrix_synapse_database_host: "your-postgres-server-hostname"
|
|
matrix_synapse_database_user: "your-postgres-server-username"
|
|
matrix_synapse_database_password: "your-postgres-server-password"
|
|
matrix_synapse_database_database: "your-postgres-server-database-name"
|
|
```
|
|
|
|
The database (as specified in `matrix_synapse_database_database`) must exist and be accessible with the given credentials.
|
|
It must be empty or contain a valid Synapse database. If empty, Synapse would populate it the first time it runs.
|
|
|
|
**Note**: the external server that you specify in `matrix_synapse_database_host` must be accessible from within the `matrix-synapse` Docker container (and possibly other containers too). This means that it either needs to be a publicly accessible hostname or that it's a hostname on the same Docker network where all containers installed by this playbook run (a network called `matrix` by default). Using a local PostgreSQL instance on the host (running on the same machine, but not in a container) is not possible. |