Matrix/matrix-docker-ansible-deploy
1
0
Fork 0
mirror of https://github.com/spantaleev/matrix-docker-ansible-deploy.git synced 2024-11-14 10:04:46 +08:00
Code Issues Packages Projects Releases Wiki Activity
d51ea25219
matrix-docker-ansible-deploy/setup.yml

41 lines
1.1 KiB
YAML
Raw Normal View History

Initial commit
2017-08-01 04:07:30 +08:00
---
- name: "Set up a Matrix server"
Fix TRANSFORM_INVALID_GROUP_CHARS deprecation warning
2019-05-21 23:39:33 +08:00
hosts: "{{ target if target is defined else 'matrix_servers' }}"
Initial commit
2017-08-01 04:07:30 +08:00
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.
2019-01-12 23:53:00 +08:00
- matrix-base
Added containerization
2020-10-17 12:21:58 +08:00
- matrix-dynamic-dns
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 23:53:00 +08:00
- matrix-mailer
- matrix-postgres
- matrix-corporal
Move matrix-appservice-discord into a separate role
2019-05-18 00:14:12 +08:00
- matrix-bridge-appservice-discord
Added Slack role
2019-06-10 22:52:48 +08:00
- matrix-bridge-appservice-slack
Add matrix-appservice-webhooks role.
2020-01-10 00:00:03 +08:00
- matrix-bridge-appservice-webhooks
Move matrix-appservice-irc into a separate role
2019-05-16 08:07:40 +08:00
- matrix-bridge-appservice-irc
Move mautrix-facebook into a separate role
2019-05-15 08:34:31 +08:00
- matrix-bridge-mautrix-facebook
add hangouts bridge by copying facebook bridge and find-replacing
2019-07-29 00:52:30 +08:00
- matrix-bridge-mautrix-hangouts
added mautrix-signal role
2020-10-23 05:29:34 +08:00
- matrix-bridge-mautrix-signal
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).
2019-05-14 22:47:22 +08:00
- matrix-bridge-mautrix-telegram
- matrix-bridge-mautrix-whatsapp
Add mx-puppet-discord
2020-06-11 23:54:36 +08:00
- matrix-bridge-mx-puppet-discord
Add mx-puppet-steam
2020-07-01 19:46:58 +08:00
- matrix-bridge-mx-puppet-steam
Initial mx-puppet-skype bridge role
2020-03-17 08:33:11 +08:00
- matrix-bridge-mx-puppet-skype
Initial mx-puppet-slack bridge role
2020-04-12 22:17:30 +08:00
- matrix-bridge-mx-puppet-slack
Add mx-puppet-twitter Signed-off-by: Tulir Asokan <tulir@maunium.net>
2020-06-29 20:28:43 +08:00
- matrix-bridge-mx-puppet-twitter
mx-puppet-instagram: add role
2020-06-27 18:40:27 +08:00
- matrix-bridge-mx-puppet-instagram
renamed role matrix-sms-bridge to matrix-bridge-sms
2020-06-05 18:25:41 +08:00
- matrix-bridge-sms
Add support for matrix-reminder-bot
2020-07-20 19:13:08 +08:00
- matrix-bot-matrix-reminder-bot
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 23:53:00 +08:00
- matrix-synapse
Add synapse-admin support Fixes #562 (Github Issue)
2020-07-22 13:10:26 +08:00
- matrix-synapse-admin
Add matrix-registration support
2020-09-01 18:46:05 +08:00
- matrix-registration
Riot is now Element Fixes #586 (Github Issue)
2020-07-17 16:31:20 +08:00
- matrix-client-element
Add Jitsi support
2020-03-23 23:19:15 +08:00
- matrix-jitsi
Rename variables (s/mxisd/ma1sd/) and adapt roles
2020-01-09 05:31:44 +08:00
- matrix-ma1sd
Implement self-hosted Dimension server
2019-03-07 13:22:08 +08:00
- matrix-dimension
Add Email2Matrix support
2019-08-05 18:06:49 +08:00
- 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.
2019-01-12 23:53:00 +08:00
- matrix-nginx-proxy
Add TLS support to Coturn
2019-03-19 16:24:39 +08:00
- matrix-coturn
Add matrix-aux role to help with managing auxiliary files/directories
2021-01-12 04:15:13 +08:00
- matrix-aux
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 23:53:00 +08:00
- matrix-common-after
Reference in New Issue Copy Permalink