Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
synapse
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Container Registry
Model registry
Operate
Terraform modules
Monitor
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Timo Ley
synapse
Commits
ba7a5238
Unverified
Commit
ba7a5238
authored
5 years ago
by
Brendan Abolivier
Browse files
Options
Downloads
Patches
Plain Diff
Argh trailing spaces
parent
e837be5b
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
docs/federate.md
+2
-2
2 additions, 2 deletions
docs/federate.md
with
2 additions
and
2 deletions
docs/federate.md
+
2
−
2
View file @
ba7a5238
...
...
@@ -10,7 +10,7 @@ The `server_name` configured in the Synapse configuration file (often
identified (eg:
`@user:example.com`
,
`#room:example.com`
). By default,
it is also the domain that other servers will use to try to reach your
server (via port 8448). This is easy to set up and will work provided
you set the
`server_name`
to match your machine's public DNS hostname.
you set the
`server_name`
to match your machine's public DNS hostname.
You will also need a valid TLS certificate for this
`server_name`
served
on port 8448 - the preferred way to do that is by using a reverse proxy,
...
...
@@ -23,7 +23,7 @@ to use port than 8448 (e.g. you want to use `example.com` as your `server_name`
but want Synapse to be reachable on
`synapse.example.com:443`
). This can
be done using delegation, which allows an admin to dictate where federation
traffic should be sent, see
[
delegate.md
](
<
delegate.md
>
)
for instructions on
how to set this up.
how to set this up.
Once federation has been configured, you should be able to join a room over
federation. A good place to start is
`#synapse:matrix.org`
- a room for
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment