5 commits

Author	SHA1	Message	Date
Slavi Pantaleev	410a915a8a	Move roles/matrix* to roles/custom/matrix* ... This paves the way for installing other roles into `roles/galaxy` using `ansible-galaxy`, similar to how it's done in: - https://github.com/spantaleev/gitea-docker-ansible-deploy - https://github.com/spantaleev/nextcloud-docker-ansible-deploy In the near future, we'll be removing a lot of the shared role code from here and using upstream roles for it. Some of the core `matrix-*` roles have already been extracted out into other reusable roles: - https://github.com/devture/com.devture.ansible.role.postgres - https://github.com/devture/com.devture.ansible.role.systemd_docker_base - https://github.com/devture/com.devture.ansible.role.timesync - https://github.com/devture/com.devture.ansible.role.vars_preserver - https://github.com/devture/com.devture.ansible.role.playbook_runtime_messages - https://github.com/devture/com.devture.ansible.role.playbook_help We just need to migrate to those.	2022-11-03 09:11:29 +02:00
Slavi Pantaleev	34cdaade08	Use fully-qualified module names for builtin Ansible modules ... Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/1939	2022-07-18 12:58:41 +03:00
Marko Weltzer	7e5b88c3b7	fix: all praise the allmighty yamllinter	2022-02-05 21:32:54 +01:00
Chris van Dijk	7585bcc4ac	Allow the matrix user username and groupname to be configured separately ... No migration steps should be required.	2020-05-01 19:59:32 +02:00
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.	2019-01-12 18:01:10 +02:00

Renamed from roles/matrix-server/tasks/setup/setup_well_known.yml (Browse further)