mirror of
https://github.com/strukturag/nextcloud-spreed-signaling
synced 2024-05-09 09:06:34 +02:00
readme: Add note on clustering.
This commit is contained in:
parent
0e144906a4
commit
5a242b2570
14
README.md
14
README.md
|
@ -157,6 +157,20 @@ proxy process gracefully after all clients have been disconnected. No new
|
||||||
publishers will be accepted in this case.
|
publishers will be accepted in this case.
|
||||||
|
|
||||||
|
|
||||||
|
### Clustering
|
||||||
|
|
||||||
|
The signaling server supports a clustering mode where multiple running servers
|
||||||
|
can be interconnected to form a single "virtual" server. This can be used to
|
||||||
|
increase the capacity of the signaling server or provide a failover setup.
|
||||||
|
|
||||||
|
For that a central NATS server / cluster must be used by all instances. Each
|
||||||
|
instance must running a GRPC server (enable `listening` in section `grpc` and
|
||||||
|
optionally setup certificate, private key and CA). The list of other GRPC
|
||||||
|
targets must be configured as `targets` in section `grpc` or can be retrieved
|
||||||
|
from an etcd cluster. See `server.conf.in` in section `grpc` for configuration
|
||||||
|
details.
|
||||||
|
|
||||||
|
|
||||||
## Setup of frontend webserver
|
## Setup of frontend webserver
|
||||||
|
|
||||||
Usually the standalone signaling server is running behind a webserver that does
|
Usually the standalone signaling server is running behind a webserver that does
|
||||||
|
|
Loading…
Reference in a new issue