0c9b609245
LiveKit server configuration was the default ones. These configurations were not connecting to any Redis instance. When running a standalone LiveKit server, Redis is not needed. However, when adding other LiveKit ecosystem service, e.g. Egress, LiveKit server publish jobs to a Redis queue, that are handled by the Egress workers. (Precisely, they use Redis Pub/Sub to communicate but I am no expert) The LiveKit server and the Egress need to be connected to the same Redis instance. This commit configure the LiveKit server before adding the Egress service to the compose stack.
6 lines
69 B
YAML
6 lines
69 B
YAML
log_level: debug
|
|
redis:
|
|
address: redis:6379
|
|
keys:
|
|
devkey: secret
|