clarify option 1

This commit is contained in:
Richard van der Hoff 2019-02-07 18:46:02 +00:00 committed by GitHub
parent d8e63846e2
commit 9b7aa543d9
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -112,7 +112,7 @@ _matrix._tcp.example.com. IN SRV 10 5 443 customer.example.net.
In this situation, you have two choices for how to proceed: In this situation, you have two choices for how to proceed:
#### Option 1: give Synapse a certificate for your matrix domain #### Option 1: give Synapse (or a reverse-proxy) a certificate for your matrix domain
Synapse 1.0 will expect your server to present a TLS certificate for your Synapse 1.0 will expect your server to present a TLS certificate for your
`server_name` (`example.com` in the above example). You can achieve this by `server_name` (`example.com` in the above example). You can achieve this by