Slavi Pantaleev 00383a73ac Make running --tags=setup-synapse only not fail to register bridges ... Until now, if `--tags=setup-synapse` was used, bridge tasks would not run and bridges would fail to register with the `matrix-synapse` role. This means that Synapse's configuration would be generated with an empty list of appservices (`app_service_config_files: []`). .. and then bridges would fail, because Synapse would not be aware of there being any bridges. From now on, bridges always run their init tasks and always register with Synapse. For the Telegram bridge, the same applies to registering with matrix-nginx-proxy. Previously, running `--tags=setup-nginx-proxy` would get rid of the Telegram endpoint configuration for the same reason. Not anymore.		2019-06-14 10:19:52 +03:00
..
defaults	Automatically force-pull :latest images	2019-06-10 14:30:28 +03:00
tasks	Make running --tags=setup-synapse only not fail to register bridges	2019-06-14 10:19:52 +03:00
templates	Delay bridge startup to ensure Synapse is up	2019-06-07 12:15:37 +03:00