51312b8250
As suggested in #63 (Github issue), splitting the playbook's logic into multiple roles will be beneficial for maintainability. This patch realizes this split. Still, some components affect others, so the roles are not really independent of one another. For example: - disabling mxisd (`matrix_mxisd_enabled: false`), causes Synapse and riot-web to reconfigure themselves with other (public) Identity servers. - enabling matrix-corporal (`matrix_corporal_enabled: true`) affects how reverse-proxying (by `matrix-nginx-proxy`) is done, in order to put matrix-corporal's gateway server in front of Synapse We may be able to move away from such dependencies in the future, at the expense of a more complicated manual configuration, but it's probably not worth sacrificing the convenience we have now. As part of this work, the way we do "start components" has been redone now to use a loop, as suggested in #65 (Github issue). This should make restarting faster and more reliable.
21 lines
957 B
YAML
21 lines
957 B
YAML
---
|
|
|
|
- set_fact:
|
|
matrix_federation_api_url_endpoint_public: "https://{{ hostname_matrix }}:8448/_matrix/federation/v1/version"
|
|
|
|
- name: Check Matrix Federation API
|
|
uri:
|
|
url: "{{ matrix_federation_api_url_endpoint_public }}"
|
|
follow_redirects: false
|
|
validate_certs: false
|
|
register: result_matrix_federation_api
|
|
ignore_errors: true
|
|
|
|
- name: Fail if Matrix Federation API not working
|
|
fail:
|
|
msg: "Failed checking Matrix Federation API is up at `{{ hostname_matrix }}` (checked endpoint: `{{ matrix_federation_api_url_endpoint_public }}`). Is Synapse running? Is port 8448 open in your firewall? Full error: {{ result_matrix_federation_api }}"
|
|
when: "result_matrix_federation_api.failed or 'json' not in result_matrix_federation_api"
|
|
|
|
- name: Report working Matrix Federation API
|
|
debug:
|
|
msg: "The Matrix Federation API at `{{ hostname_matrix }}` (checked endpoint: `{{ matrix_federation_api_url_endpoint_public }}`) is working" |