mirror of
https://github.com/spantaleev/matrix-docker-ansible-deploy.git
synced 2024-09-22 01:54:16 +00:00
df8d9cfd34
The answer to these is: it's good to have them in both places. The role defines the obvious things it depends on (not knowing what setup it will find itself into), and then `group_vars/matrix_servers` "extends" it based on everything else it knows (the homeserver being Synapse, whether or not the internal Postgres server is being used, etc.) |
||
---|---|---|
.. | ||
matrix-base | ||
matrix-bot-matrix-reminder-bot | ||
matrix-bridge-appservice-discord | ||
matrix-bridge-appservice-irc | ||
matrix-bridge-appservice-slack | ||
matrix-bridge-appservice-webhooks | ||
matrix-bridge-mautrix-facebook | ||
matrix-bridge-mautrix-hangouts | ||
matrix-bridge-mautrix-signal | ||
matrix-bridge-mautrix-telegram | ||
matrix-bridge-mautrix-whatsapp | ||
matrix-bridge-mx-puppet-discord | ||
matrix-bridge-mx-puppet-instagram | ||
matrix-bridge-mx-puppet-skype | ||
matrix-bridge-mx-puppet-slack | ||
matrix-bridge-mx-puppet-steam | ||
matrix-bridge-mx-puppet-twitter | ||
matrix-bridge-sms | ||
matrix-client-element | ||
matrix-common-after/tasks | ||
matrix-corporal | ||
matrix-coturn | ||
matrix-dimension | ||
matrix-dynamic-dns | ||
matrix-email2matrix | ||
matrix-jitsi | ||
matrix-ma1sd | ||
matrix-mailer | ||
matrix-nginx-proxy | ||
matrix-postgres | ||
matrix-registration | ||
matrix-synapse | ||
matrix-synapse-admin |