finallycoffee/matrix-docker-ansible-deploy
finallycoffee/matrix-docker-ansible-deploy
2
1
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Document difference between matrix_homeserver_container_url and matrix_addons_homeserver_client_api_url

Browse Source
This commit is contained in:
Slavi Pantaleev 2024-01-13 18:07:00 +02:00
parent ed63068e22
commit b9dfa87f9a
1 changed files with 4 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
roles/custom/matrix-base/defaults/main.yml
View File

@ -26,6 +26,8 @@ matrix_addons_container_network: matrix-addons
matrix_addons_homeserver_container_network: "{{ matrix_homeserver_container_network }}"
# The URL where addon services (bridges, bots, etc.) can reach the homeserver.
# By default, this is configured to go directly to the homeserver, but the playbook may
# override it to go through an intermediary service.
matrix_addons_homeserver_client_api_url: "{{ matrix_homeserver_container_url }}"
# The systemd services (representing the homeserver) that addon services (bridges, bots, etc.) should depend on
@ -151,6 +153,8 @@ matrix_homeserver_container_network: "matrix-homeserver"
matrix_homeserver_systemd_services_list: []
# Specifies where the homeserver's Client-Server API is on the container network (matrix_homeserver_container_network).
# Most services that need to reach the homeserver do not use `matrix_homeserver_container_url`, but
# rather `matrix_addons_homeserver_client_api_url`.
matrix_homeserver_container_url: "http://{{ matrix_homeserver_container_client_api_endpoint }}"
# Specifies where the homeserver's Client-Server API is on the container network (matrix_homeserver_container_network).