From 69776ba08e14b264cff7c02d8abd465591bd091d Mon Sep 17 00:00:00 2001 From: fkwp Date: Wed, 6 Nov 2024 19:58:48 +0100 Subject: [PATCH] add .well-known section including a note that this is not effective for the local dev environment --- backend/tls_localhost_nginx.conf | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/backend/tls_localhost_nginx.conf b/backend/tls_localhost_nginx.conf index 2e2b8655..19efa5ba 100644 --- a/backend/tls_localhost_nginx.conf +++ b/backend/tls_localhost_nginx.conf @@ -9,6 +9,18 @@ server { ssl_certificate /root/ssl/cert.pem; ssl_certificate_key /root/ssl/key.pem; + # well-known config adding rtc_foci backend + # Note well-known is currently not effective due to: + # https://spec.matrix.org/v1.12/client-server-api/#well-known-uri the spec + # says it must be at https://$server_name/... (implied port 443) Hence, we + # currently rely for local development environment on depricated config.json + # setting for livekit_service_url + location /.well-known/matrix/client { + return 200 '{"m.homeserver": {"base_url": "http://synapse.localhost:8008"}, "org.matrix.msc4143.rtc_foci": [{"type": "livekit", "livekit_service_url": "http://localhost:8080"}]}'; + default_type application/json; + add_header Access-Control-Allow-Origin *; + } + # Reverse proxy for Matrix Synapse Homeserver # This is also required for development environment. # Reason: the lk-jwt-service uses the federation API for the openid token