Skip to content
Snippets Groups Projects
Commit a7f470d1 authored by Matthew Hodgson's avatar Matthew Hodgson
Browse files

more README fixes

parent 428581dd
No related branches found
No related tags found
No related merge requests found
Hide whitespace changes
Inline Side-by-side
Showing
with 3 additions and 1 deletion
README.rst
+ 3
− 1
View file @ a7f470d1
...@@ -223,7 +223,7 @@ IDs: ...@@ -223,7 +223,7 @@ IDs:
domain name. domain name.
For the first form, simply pass the required hostname (of the machine) as the For the first form, simply pass the required hostname (of the machine) as the
--host parameter:: --server-name parameter::
$ python -m synapse.app.homeserver \ $ python -m synapse.app.homeserver \
--server-name machine.my.domain.name \ --server-name machine.my.domain.name \
...@@ -239,8 +239,10 @@ and port where the server is running. (At the current time synapse does not ...@@ -239,8 +239,10 @@ and port where the server is running. (At the current time synapse does not
support clustering multiple servers into a single logical homeserver). The DNS support clustering multiple servers into a single logical homeserver). The DNS
record would then look something like:: record would then look something like::
$ dig -t srv _matrix._tcp.machine.my.domaine.name
_matrix._tcp IN SRV 10 0 8448 machine.my.domain.name. _matrix._tcp IN SRV 10 0 8448 machine.my.domain.name.
At this point, you should then run the homeserver with the hostname of this At this point, you should then run the homeserver with the hostname of this
SRV record, as that is the name other machines will expect it to have:: SRV record, as that is the name other machines will expect it to have::
......
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment