docker/livekit/config/livekit-server.yaml

log_level: debug
redis:
  address: redis:6379
keys:
  devkey: secret

webhook:
  api_key: devkey
  urls:
      - http://app-dev:8000/api/v1.0/rooms/webhooks-livekit/
🔧(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. 2024-07-05 16:36:41 +02:00			`log_level: debug`
			`redis:`
			`address: redis:6379`
			`keys:`
			`devkey: secret`
🔧(compose) configure LiveKit webhooks in the local Docker Compose stack Without this configuration, LiveKit does not notify the backend when a recording starts, leaving it stuck in a “starting recording” state. Thanks to @leobouloc for spotting the issue. 2026-01-29 17:50:39 +01:00
			`webhook:`
			`api_key: devkey`
			`urls:`
			`- http://app-dev:8000/api/v1.0/rooms/webhooks-livekit/`