From 9ffadcdbadd1d480a23a8fc46111bba211089006 Mon Sep 17 00:00:00 2001 From: Richard van der Hoff <1389908+richvdh@users.noreply.github.com> Date: Fri, 15 Mar 2019 09:43:24 +0000 Subject: [PATCH 1/2] fix some typos in federate.md --- docs/federate.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/docs/federate.md b/docs/federate.md index 186245a94..b7fc09661 100644 --- a/docs/federate.md +++ b/docs/federate.md @@ -15,8 +15,8 @@ machine's public DNS hostname, and provide Synapse with a TLS certificate which is valid for your ``server_name``. Once you have completed the steps necessary to federate, you should be able to -join a room via federation. (A good place to start is ``#synapse:matrix.org`` -- a room for Synapse admins.) +join a room via federation. (A good place to start is ``#synapse:matrix.org`` - a +room for Synapse admins.) ## Delegation @@ -89,7 +89,6 @@ In our example, we would need to add this SRV record in the _matrix._tcp.example.com. 3600 IN SRV 10 5 443 synapse.example.com. - Once done and set up, you can check the DNS record with ``dig -t srv _matrix._tcp.``. In our example, we would expect this: @@ -117,7 +116,6 @@ you invite them to. This can be caused by an incorrectly-configured reverse proxy: see [reverse_proxy.rst]() for instructions on how to correctly configure a reverse proxy. - ## Running a Demo Federation of Synapses If you want to get up and running quickly with a trio of homeservers in a From 9482a84c0a12abeae40119da2f78e84908a1591b Mon Sep 17 00:00:00 2001 From: Michael Kaye <1917473+michaelkaye@users.noreply.github.com> Date: Tue, 19 Mar 2019 10:37:18 +0000 Subject: [PATCH 2/2] Repoint docs for federation (#4881) --- changelog.d/4881.misc | 1 + docs/reverse_proxy.rst | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) create mode 100644 changelog.d/4881.misc diff --git a/changelog.d/4881.misc b/changelog.d/4881.misc new file mode 100644 index 000000000..308c21c83 --- /dev/null +++ b/changelog.d/4881.misc @@ -0,0 +1 @@ +Update link to federation docs. diff --git a/docs/reverse_proxy.rst b/docs/reverse_proxy.rst index 4706061eb..cc6e66a8f 100644 --- a/docs/reverse_proxy.rst +++ b/docs/reverse_proxy.rst @@ -18,7 +18,7 @@ servers do not necessarily need to connect to your server via the same server name or port. Indeed, clients will use port 443 by default, whereas servers default to port 8448. Where these are different, we refer to the 'client port' and the 'federation port'. See `Setting up federation -<../README.rst#setting-up-federation>`_ for more details of the algorithm used for +`_ for more details of the algorithm used for federation connections. Let's assume that we expect clients to connect to our server at