mirrors/synapse
1
0
Fork 0
mirror of https://github.com/element-hq/synapse.git synced 2024-12-21 03:42:55 +03:00
Code Issues Projects Releases Packages Wiki Activity

Update README.rst

Browse source
This commit is contained in:
Neil Johnson 2019-02-28 15:20:40 +00:00 committed by GitHub
parent b452b47a38
commit b649d59332
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
README.rst
View file

@ -248,8 +248,8 @@ Note that the server hostname cannot be an alias (CNAME record): it has to point
directly to the server hosting the synapse instance. directly to the server hosting the synapse instance.
If it is not possible to acquire a certificate valid for you matrix domain, If it is not possible to acquire a certificate valid for you matrix domain,
the correct method is create a Well Known entry. For more details on how to the correct method is create a .well-known entry. For more details on how to
configure Well Known `see <https://github.com/matrix-org/synapse/blob/master/docs/well_known.md`_ configure .well-known `see <https://github.com/matrix-org/synapse/blob/master/docs/well_known.md`_
For those of you upgrading your TLS certificate in readiness for Synapse 1.0, For those of you upgrading your TLS certificate in readiness for Synapse 1.0,
please take a look at `our guide <https://github.com/matrix-org/synapse/blob/master/docs/MSC1711_certificates_FAQ.md#configuring-certificates-for-compatibility-with-synapse-100>`_ please take a look at `our guide <https://github.com/matrix-org/synapse/blob/master/docs/MSC1711_certificates_FAQ.md#configuring-certificates-for-compatibility-with-synapse-100>`_