clarifying where well-known files are created
This commit is contained in:
parent
76bfe9a0ea
commit
527f5bc469
@ -46,7 +46,7 @@ If you decide to go this route, you don't need to read ahead in this document. W
|
|||||||
|
|
||||||
If you're managing the base domain by yourself somehow, you'll need to set up serving of some `/.well-known/matrix/*` files from it via HTTPS.
|
If you're managing the base domain by yourself somehow, you'll need to set up serving of some `/.well-known/matrix/*` files from it via HTTPS.
|
||||||
|
|
||||||
To make things easy for you to set up, this playbook generates and hosts 2 well-known files on the Matrix domain's server (e.g. `https://matrix.example.com/.well-known/matrix/server` and `https://matrix.example.com/.well-known/matrix/client`), even though this is the wrong place to host them.
|
To make things easy for you to set up, this playbook generates and hosts 2 well-known files on the Matrix domain's server. The files are generated at `/matrix/static-files/.well-known/matrix/` and hosted at `https://matrix.example.com/.well-known/matrix/server` and `https://matrix.example.com/.well-known/matrix/client`, even though this is the wrong place to host them.
|
||||||
|
|
||||||
You have 3 options when it comes to installing the files on the base domain's server:
|
You have 3 options when it comes to installing the files on the base domain's server:
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user