Fix Hookshot URL path generation regression
Regression since 7891268873
,
where I removed the `matrix_hookshot_urlprefix` prefix group
`group_vars/matrix_servers`, thinking the value in `roles/custom/matrix-bridge-hookshot/defaults/main.yml`
was the same.
The value in `defaults/main.yml` incorrectly included `matrix_hookshot_public_endpoint`
in `matrix_hookshot_urlprefix`, which was leading to double-`/hookshot`-prefixing.
We were previously saved by the `matrix_hookshot_urlprefix` override in `group_vars/matrix_servers`.
This fix brings the correct URL prefix value (the one without `matrix_hookshot_public_endpoint`)
to `defaults/main.yml`.
This commit is contained in:
parent
e3cbc61804
commit
ea22acc899
@ -34,7 +34,11 @@ matrix_hookshot_public_scheme: https
|
|||||||
matrix_hookshot_public_hostname: "{{ matrix_server_fqn_matrix }}"
|
matrix_hookshot_public_hostname: "{{ matrix_server_fqn_matrix }}"
|
||||||
matrix_hookshot_public_endpoint: /hookshot
|
matrix_hookshot_public_endpoint: /hookshot
|
||||||
|
|
||||||
matrix_hookshot_urlprefix: "{{ matrix_hookshot_public_scheme }}://{{ matrix_hookshot_public_hostname }}{{ matrix_hookshot_public_endpoint }}"
|
# This is the base URL prefix shared among all endpoints.
|
||||||
|
#
|
||||||
|
# It intentionally does not include the path prefix (`matrix_hookshot_public_endpoint`),
|
||||||
|
# because of how it's used - it's concatenated with paths that already use matrix_hookshot_public_endpoint` within them.
|
||||||
|
matrix_hookshot_urlprefix: "{{ matrix_hookshot_public_scheme }}://{{ matrix_hookshot_public_hostname }}"
|
||||||
|
|
||||||
# There is no need to edit ports. use matrix_hookshot_container_http_host_bind_ports below to expose ports instead.
|
# There is no need to edit ports. use matrix_hookshot_container_http_host_bind_ports below to expose ports instead.
|
||||||
matrix_hookshot_appservice_port: 9993
|
matrix_hookshot_appservice_port: 9993
|
||||||
|
Loading…
Reference in New Issue
Block a user