matrix-docker-ansible-deploy/setup.yml

---
- name: "Set up a Matrix server"
  hosts: "{{ target if target is defined else 'matrix_servers' }}"
  become: true

  roles:
    - matrix-base
    - matrix-mailer
    - matrix-postgres
    - matrix-corporal
    - matrix-bridge-appservice-discord
    - matrix-bridge-appservice-slack
    - matrix-bridge-appservice-webhooks
    - matrix-bridge-appservice-irc
    - matrix-bridge-mautrix-facebook
    - matrix-bridge-mautrix-hangouts
    - matrix-bridge-mautrix-telegram
    - matrix-bridge-mautrix-whatsapp
    - matrix-bridge-mx-puppet-skype
    - matrix-bridge-mx-puppet-slack
    - matrix-bridge-mx-puppet-instagram
    - matrix-bridge-sms
    - matrix-synapse
    - matrix-riot-web
    - matrix-jitsi
    - matrix-ma1sd
    - matrix-dimension
    - matrix-email2matrix
    - matrix-nginx-proxy
    - matrix-coturn
    - matrix-common-after
Initial commit 7 years ago			`---`
			`- name: "Set up a Matrix server"`
Fix TRANSFORM_INVALID_GROUP_CHARS deprecation warning 6 years ago			`hosts: "{{ target if target is defined else 'matrix_servers' }}"`
Initial commit 7 years ago			`become: true`

			`roles:`
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			`- matrix-base`
			`- matrix-mailer`
			`- matrix-postgres`
			`- matrix-corporal`
Move matrix-appservice-discord into a separate role 6 years ago			`- matrix-bridge-appservice-discord`
Added Slack role 6 years ago			`- matrix-bridge-appservice-slack`
Add matrix-appservice-webhooks role. 5 years ago			`- matrix-bridge-appservice-webhooks`
Move matrix-appservice-irc into a separate role 6 years ago			`- matrix-bridge-appservice-irc`
Move mautrix-facebook into a separate role 6 years ago			`- matrix-bridge-mautrix-facebook`
add hangouts bridge by copying facebook bridge and find-replacing 5 years ago			`- matrix-bridge-mautrix-hangouts`
Move mautrix telegram and whatsapp into separate roles The goal is to move each bridge into its own separate role. This commit starts off the work on this with 2 bridges: - mautrix-telegram - mautrix-whatsapp Each bridge's role (including these 2) is meant to: - depend only on the matrix-base role - integrate nicely with the matrix-synapse role (if available) - integrate nicely with the matrix-nginx-proxy role (if available and if required). mautrix-telegram bridge benefits from integrating with it. - not break if matrix-synapse or matrix-nginx-proxy are not used at all This has been provoked by #174 (Github Issue). 6 years ago			`- matrix-bridge-mautrix-telegram`
			`- matrix-bridge-mautrix-whatsapp`
Initial mx-puppet-skype bridge role 5 years ago			`- matrix-bridge-mx-puppet-skype`
Initial mx-puppet-slack bridge role 5 years ago			`- matrix-bridge-mx-puppet-slack`
mx-puppet-instagram: add role 4 years ago			`- matrix-bridge-mx-puppet-instagram`
renamed role matrix-sms-bridge to matrix-bridge-sms 5 years ago			`- matrix-bridge-sms`
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			`- matrix-synapse`
			`- matrix-riot-web`
Add Jitsi support 5 years ago			`- matrix-jitsi`
Rename variables (s/mxisd/ma1sd/) and adapt roles 5 years ago			`- matrix-ma1sd`
Implement self-hosted Dimension server 6 years ago			`- matrix-dimension`
Add Email2Matrix support 5 years ago			`- matrix-email2matrix`
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			`- matrix-nginx-proxy`
Add TLS support to Coturn 6 years ago			`- matrix-coturn`
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			`- matrix-common-after`