4 commits

Author	SHA1	Message	Date
Slavi Pantaleev	5da31ba579	Move configuration templates outside of defaults/main.yml files	2020-06-03 09:33:28 +03:00
Slavi Pantaleev	4e8543ce21	Make Telegram bridge configuration playbook-managed	2019-06-15 09:43:43 +03:00
Slavi Pantaleev	a9953dd641	Make Facebook/Telegram bridges not log to files ... We log to journald anyway. There's no need for double-logging. It should not that matrix-synapse logs to journald and to files, but that's likely to change in the future as well. Because Synapse's logs are insanely verbose right now (and may get dropped by journald), it's more reliable to have file-logging too. As Synapse matures and gets more stable, logging should hopefully get less, we should be able to only use journald and stop writing to files for it as well.	2019-06-07 15:48:13 +03:00
Slavi Pantaleev	bb816df557	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 23:47:22 +09:00

Renamed from roles/matrix-synapse/templates/ext/mautrix-telegram/config.yaml.j2 (Browse further)