Session Data (Redis)
The OpenTalk controller can be run in standalone mode, where a single
opentalk-controller provides the web api and signaling service, or it can run
in a clustered mode, where multiple opentalk-controller nodes provide
the service in parallel and synchronize through Redis
for caching data related to a video conference session.
Up until version v0.14 of the opentalk-controller, the redis service was
mandatory, starting with v0.15 it is possible to leave the whole configuration
section out to operate the controller in standalone mode.
Configuration
The section in the configuration file is called redis.
| Field | Type | Required | Default value | Description |
|---|---|---|---|---|
url | string | no | "redis://localhost:6379/" | TCP port number where the Redis server can be reached |
Examples
Default Setup
The default setup since 0.15 is to leave the [redis] section out entirely,
therefore operating the opentalk-controller in standalone mode.
# [redis]
#url = "redis://localhost:6379/"
Default Redis URL
Using the default redis url requires the [redis] section to be present. If the
url field is absent, then the default redis URL will be used. This was the
default configuration up until v0.14 of the OpenTalk controller.
[redis]
#url = "redis://localhost:6379/"
Custom Redis URL
A custom Redis URL can be specified as following:
[redis]
url = "redis://localhost:6399/"