🔧(livekit) connect LiveKit server to Redis
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.
This commit is contained in:
committed by
aleb_the_flash
parent
31ea621e44
commit
0c9b609245
5
docker/livekit/config/livekit-server.yaml
Normal file
5
docker/livekit/config/livekit-server.yaml
Normal file
@@ -0,0 +1,5 @@
|
||||
log_level: debug
|
||||
redis:
|
||||
address: redis:6379
|
||||
keys:
|
||||
devkey: secret
|
||||
Reference in New Issue
Block a user