If the playbook were to run with `--tags=setup-nginx-proxy`, it wouldn't go into `setup_corporal.yml`, which meant it wouldn't perform a bunch of `set_fact` calls which override important nginx proxy configuration. We run these variable overrides on each call now (tagged with `always`) to avoid such problems in the future.development
parent
0d0ccde286
commit
2df4349606
@ -0,0 +1,11 @@
|
|||||||
|
# These overrides run with the `always` tag,
|
||||||
|
# because they're important not only for the `setup-corporal` tag, but for other tags too.
|
||||||
|
#
|
||||||
|
# We want an nginx-proxy rebuild (`--tags=setup-nginx-proxy`) to also go through here
|
||||||
|
# and be affected by these overrides.
|
||||||
|
|
||||||
|
- name: Override configuration specifying where the Matrix Client API is
|
||||||
|
set_fact:
|
||||||
|
matrix_nginx_proxy_matrix_client_api_addr_with_proxy_container: "matrix-corporal:41080"
|
||||||
|
matrix_nginx_proxy_matrix_client_api_addr_sans_proxy_container: "localhost:41080"
|
||||||
|
when: "matrix_corporal_enabled"
|
Loading…
Reference in new issue