Skip to content

Commit 4f26d6e

Browse files
authored
Merge pull request #696 from strukturag/update-readme
Remove deprecated section on multiple signaling servers from README.
2 parents 879e1ca + ddfd976 commit 4f26d6e

File tree

1 file changed

+0
-20
lines changed

1 file changed

+0
-20
lines changed

README.md

Lines changed: 0 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -380,23 +380,3 @@ Usage:
380380
config file to use (default "server.conf")
381381
-maxClients int
382382
number of client connections (default 100)
383-
384-
385-
## Running multiple signaling servers
386-
387-
IMPORTANT: This is considered experimental and might not work with all
388-
functionality of the signaling server, especially when using the Janus
389-
integration.
390-
391-
The signaling server uses the NATS server to send messages to peers that are
392-
not connected locally. Therefore multiple signaling servers running on different
393-
hosts can use the same NATS server to build a simple cluster, allowing more
394-
simultaneous connections and distribute the load.
395-
396-
To set this up, make sure all signaling servers are using the same settings for
397-
their `session` keys and the `secret` in the `backend` section. Also the URL to
398-
the NATS server (option `url` in section `nats`) must point to the same NATS
399-
server.
400-
401-
If all this is setup correctly, clients can connect to either of the signaling
402-
servers and exchange messages between them.

0 commit comments

Comments
 (0)