matrix-docker-ansible-deploy/roles/matrix-bridge-mautrix-telegram/tasks
Slavi Pantaleev 5361d3a412 Fix Telegram bridge proxying config when matrix-nginx-proxy disabled
Related to #189 (Github Issue).

People had proxying problems if:
- they used the whole playbook (including the `matrix-nginx-proxy` role)
- and they were disabling the proxy (`matrix_nginx_proxy_enabled: false`)
- and they were proxying with their own nginx server

For them,
`matrix_nginx_proxy_proxy_matrix_additional_server_configuration_blocks`
would not be modified to inject the necessary proxying configuration.
2019-05-27 10:04:52 +03:00
..
init.yml Fix CONDITIONAL_BARE_VARS deprecation warning in ansible 2.8 2019-05-21 10:25:59 -05:00
main.yml Fix CONDITIONAL_BARE_VARS deprecation warning in ansible 2.8 2019-05-21 10:25:59 -05:00
setup_install.yml Fix Telegram bridge proxying config when matrix-nginx-proxy disabled 2019-05-27 10:04:52 +03:00
setup_uninstall.yml Make bridge uninstallation stop services 2019-05-21 11:27:09 +09:00
validate_config.yml Fix Telegram bridge HTTP proxying when not using matrix-nginx-proxy 2019-05-26 20:50:52 +03:00