offer experimental livekit integration#385
Conversation
|
LiveKit API secrets are just random strings, we can generate those ourselves (e.g. using If we control the key and secret, we can generate the full config file without slurping and follow the same concept as for the other config files -> merge a role-defined Would you like to try that? Just make sure to to the other places where the key needs to be replaced are also all managed or fixed by the role ( That's my only nitpick by the way, the PR looks really good :) Thanks! |
|
Oh and we may need systemd overrides for |
|
Looks good to me! I'll try to give it a spin later this week on our infra and the merge :) |
This pull request introduces the option to enable livekit as media streaming backend as currently described in https://docs.bigbluebutton.org/new-features/#integration-with-livekit.
I tried to follow the patterns and structure this ansible role already uses. Please inform me where I might have it misunderstood.
It was a bit more tricky than I initially thought, because livekit-server currently generates an api-key-pair during install (see https://github.com/bigbluebutton/bigbluebutton/blob/v3.0.x-release/build/packages-template/bbb-livekit/after-install.sh#L4) that needs to be taken into account when handling the configuration files in
/etc/bigbluebutton/.