Files
computer-playbook/roles/web-app-opentalk/templates/livekit.yaml.j2
kevinveenbirkenbachandClaude Fable 5 0857f5ec83 fix(opentalk): migrate controller config to v0.34 and serve TURN via livekit
Controller v0.34 restructured its configuration: the top-level livekit,
turn, stun and log keys are gone, livekit now lives under the mandatory
roomserver section (run internally via kind=internal) and
http.service_api_keys became required for the roomserver integration
(new service_api_secret credential). TURN moves to the livekit embedded
server on the stun_turn band port 3479 since the controller no longer
brokers coturn to clients. Verified by booting controller v0.34.1 with
the rendered template (settings load, startup reaches the DB connect)
and livekit v1.13.3 with the TURN block (TURN server starts). LiveKit
and controller ports resolve from the services.yml ports SPOT instead
of hardcoded values.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-12 03:15:52 +02:00

17 lines
412 B
Django/Jinja

port: {{ OPENTALK_LIVEKIT_HTTP_PORT }}
log_level: info
rtc:
tcp_port: {{ OPENTALK_LIVEKIT_TCP_PORT }}
port_range_start: {{ OPENTALK_LIVEKIT_RTC_START }}
port_range_end: {{ OPENTALK_LIVEKIT_RTC_END }}
use_external_ip: true
turn:
enabled: true
udp_port: {{ OPENTALK_LIVEKIT_TURN_UDP_PORT }}
domain: {{ OPENTALK_DOMAIN }}
keys:
{{ OPENTALK_LIVEKIT_API_KEY }}: "{{ OPENTALK_LIVEKIT_API_SECRET }}"