839b401b28
Until now, we were starting from a fresh configuration, as generated by Synapse and manipulating it with regex and line replacements, until we made it work. This is more fragile and less predictable, so we're moving to a static configuration file generated from a Jinja template. The upside is that configuration will be stable and predictable. The downside of this new approach is that any manual configuration changes after the playbook is done, will be thrown away on future playbook invocations. There are 2 ways to work around the need for manual configuration changes though: - making them part of this playbook and its default template configuration files (which benefits everyone) - going your own way for a given host and overriding the template files that gets used (that is, the `matrix_synapse_template_synapse_homeserver` or `matrix_synapse_template_synapse_log` variables) |
||
|---|---|---|
| .. | ||
| coturn | ||
| cron.d | ||
| env | ||
| nginx-conf.d | ||
| riot-web | ||
| synapse | ||
| systemd | ||
| usr-local-bin | ||
| s3fs-credentials.j2 | ||