Logo
Explore Help
Sign In
studio/meet
2
0
Fork 0
You've already forked meet
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
980d3c19d817d8a59d2fceef685c092fd729e9d2
meet/docker/livekit/config/livekit-server.yaml

6 lines
69 B
YAML
Raw Normal View History

🔧(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
Reference in New Issue Copy Permalink
Powered by Gitea Version: 1.25.4 Page: 34ms Template: 2ms
English
Bahasa Indonesia Deutsch English Español Français Gaeilge Italiano Latviešu Magyar nyelv Nederlands Polski Português de Portugal Português do Brasil Suomi Svenska Türkçe Čeština Ελληνικά Български Русский Українська فارسی മലയാളം 日本語 简体中文 繁體中文(台灣) 繁體中文(香港) 한국어
Licenses API