You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Slavi Pantaleev 51312b8250 Split playbook into multiple roles ... 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.		6 years ago
..
ext	Split playbook into multiple roles	6 years ago
import_media_store.yml	Split playbook into multiple roles	6 years ago
init.yml	Split playbook into multiple roles	6 years ago
main.yml	Split playbook into multiple roles	6 years ago
register_user.yml	Split playbook into multiple roles	6 years ago
self_check_client_api.yml	Split playbook into multiple roles	6 years ago
self_check_federation_api.yml	Split playbook into multiple roles	6 years ago
setup_synapse_entrypoint.yml	Split playbook into multiple roles	6 years ago
setup_synapse_goofys.yml	Split playbook into multiple roles	6 years ago
setup_synapse_main.yml	Split playbook into multiple roles	6 years ago
setup_synapse_pre.yml	Split playbook into multiple roles	6 years ago