5 Commits (f97175a1c6a6ddfa457d7f15d7bd8c52e5660c15)

Author	SHA1	Message	Date
Slavi Pantaleev	4e8543ce21	Make Telegram bridge configuration playbook-managed	2019-06-15 09:43:43 +03:00
Slavi Pantaleev	d6d6c152a3	Delay bridge startup to ensure Synapse is up ... Bridges start matrix-synapse.service as a dependency, but Synapse is sometimes slow to start, while bridges are quick to hit it and die (if unavailable). They'll auto-restart later, but .. this still breaks `--tags=start`, which doesn't wait long enough for such a restart to happen. This attempts to slow down bridge startup enough to ensure Synapse is up and no failures happen at all.	2019-06-07 12:15:37 +03:00
Slavi Pantaleev	7379968a3c	Fix Telegram bridge HTTP proxying when not using matrix-nginx-proxy ... From what I see, this was never implemented to begin with. Fixes #189 (Github Issue).	2019-05-26 20:50:52 +03:00
Slavi Pantaleev	13c4e7e5b6	Merge branch 'master' into separate-bridge-roles	2019-05-16 09:45:06 +09: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