Open-source Livekit documentation

[NousernameSad2]

Self-hosting Huly comes with a few trade-offs that can be worked around with some coding knowledge. However, the integration with LiveKit in the open-source version presents significant challenges that could benefit from better documentation. While we love using Huly as our team collaboration platform and have successfully navigated most self-hosting aspects, setting up the video/audio functionality remains a major problem (at least from our use-case). A step-by-step tutorial or guide for the open-source version of LiveKit integration would be immensely helpful for teams looking to self-host Huly with full communication capabilities. We're sharing this feedback because Huly has been an excellent platform for our team, and we'd love to see more organizations able to benefit from its complete feature set in their self-hosted environments.

If helpful, our team of tech enthusiasts can provide detailed information about the specific errors we've encountered and share insights from our deployment experience to assist with documentation development.

Regards

[alternativniy]

If it's not too much trouble, could you share the result? Did you manage to fully integrate the local LiveKit?

If so, could you please share the instructions?

[NousernameSad2]

If it's not too much trouble, could you share the result? Did you manage to fully integrate the local LiveKit?

If so, could you please share the instructions?

Unfortunately, we were not able to fully integrate the open source version of livekit. We are still currently using the cloud version to avoid further complications.

[shanzez]

If you wouldn't mind, it would at least be helpful to see your integration steps to use the cloud version.

[sh4hzaib]

I was able to selfhost Livekit
https://docs.livekit.io/home/self-hosting/vm/

the only problem I faced was my docker containers keep restarting, this was due to not being connected to redis
for the time being I'm using this configuration.

bind 127.0.0.1 ::1
protected-mode yes
port 6379
timeout 0
tcp-keepalive 300