meta data for this page
  •  

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
Next revision Both sides next revision
digital:server:matrixsynapsemisc [2019/01/28 17:28]
natrius 		digital:server:matrixsynapsemisc [2020/06/17 18:40]
natrius
Line 3: Line 3:
 Different things, sometimes advanced and some things that just did not fit in the regular guide.  Different things, sometimes advanced and some things that just did not fit in the regular guide. 
  
-## .well-known section +## Show the public rooms on the server
-Mathijs   +
-it's a little early, but you could also add a section about .well-known +
-which just means you have nginx serve a json file on example.com/.well-known/matrix/client +
-I did it for apache, but it's probably fairly easy for nginx as well +
- +
-Mathijs   +
-https://matrix.org/docs/spec/client_server/r0.4.0.html#server-discovery +
-if you like reading spec :) +
- +
-## Coturn +
- +
-Coturn is a turn server and it is used for 1:1 voip calls through the client (example: riot). +
- +
-<code>apt install coturn</code> +
- +
-Edit Config files +
- +
-opening ports+
  
 +''https://example.com/_matrix/client/r0/publicRooms''
  
 ## Add an SRV Record ## Add an SRV Record
Line 53: Line 36:
  
 It's so your server_name (what's in MXIDs) doesn't have to be the hostname of the machine synapse is running on. It's so your server_name (what's in MXIDs) doesn't have to be the hostname of the machine synapse is running on.
 +
 +### Example 1
 +
 +''example.com'' points to the physical machine where synapse is installed and Port 8448 is used. 
 +
 +### Example 2
 +
 +''example.com'' points to the phsycial machine where synapse is installes and port 8448 can not be used. 
 +
 +SRV needed. 
 +
 +### Example 3
 +
 +FIXME ''example.com'' point to the physical machine with the URL ''example1.com''
 +
 +SRV needed?
 +
 +#### Set up SRV (**DON'T DO IT IF YOU HAVE SET UP WELL.KNOWN ALREADY!**)
 +
 +By setting an SRV record in your DNS provider, it is possible to tell other matrix servers where to connect to the server, pointing them to the correct hostname and port, in this example the default port (8448) is still used:
 +
 +<code>
 +_matrix._tcp.example.com. 3600 IN SRV 10 5 443 synapse.example.com.
 +</code>
 +
 +There is still an A record needed, pointing to the IP-addess of synapse on the subdomain (matrix.example.com). This way others can add your user with ''@user:example.com'' instead of ''@user:matrix.example.com''.
 +
 +
 +## .well-known section
 +
 +Mathijs  
 +it's a little early, but you could also add a section about .well-known
 +which just means you have nginx serve a json file on example.com/.well-known/matrix/client
 +I did it for apache, but it's probably fairly easy for nginx as well
 +
 +Mathijs  
 +https://matrix.org/docs/spec/client_server/r0.4.0.html#server-discovery
 +if you like reading spec :)
 +
 +#### Proper explanation
 +
 +.well-known will be checked before SRV gets checked. 
 +
 +## Coturn
 +
 +Coturn is a turn server and it is used for 1:1 voip calls through the client (example: riot).
 +
 +<code>apt install coturn</code>
 +
 +Edit Config files
 +
 +opening ports
  
 ## Optional Adminshell ## Optional Adminshell