From 0c9b60924588cc70221a959997726f234a081d76 Mon Sep 17 00:00:00 2001 From: antoine lebaud Date: Fri, 5 Jul 2024 16:36:41 +0200 Subject: [PATCH] =?UTF-8?q?=F0=9F=94=A7(livekit)=20connect=20LiveKit=20ser?= =?UTF-8?q?ver=20to=20Redis?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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. --- docker-compose.yml | 6 +++++- docker/livekit/config/livekit-server.yaml | 5 +++++ 2 files changed, 10 insertions(+), 1 deletion(-) create mode 100644 docker/livekit/config/livekit-server.yaml diff --git a/docker-compose.yml b/docker-compose.yml index 098e0845..f5df29f4 100644 --- a/docker-compose.yml +++ b/docker-compose.yml @@ -153,8 +153,12 @@ services: livekit: image: livekit/livekit-server - entrypoint: /livekit-server --dev --bind 0.0.0.0 + entrypoint: /livekit-server --dev --bind 0.0.0.0 --config ./config.yaml ports: - "7880:7880" - "7881:7881" - "7882:7882/udp" + volumes: + - ./docker/livekit/config/livekit-server.yaml:/config.yaml + depends_on: + - redis diff --git a/docker/livekit/config/livekit-server.yaml b/docker/livekit/config/livekit-server.yaml new file mode 100644 index 00000000..3de4e707 --- /dev/null +++ b/docker/livekit/config/livekit-server.yaml @@ -0,0 +1,5 @@ +log_level: debug +redis: + address: redis:6379 +keys: + devkey: secret