Hello! I’m new here, this is my first experience with Openvidu and I’ve had a lot of doubts, questions and errors, and I haven’t found a good place to turn… there are some documents, code and videos, but everything is sufficient… I’m having a lot of difficulty running it.
Well, I managed to create the localhost with Openvidu… but when I try to create the room in Call, the error “Failed to create room” appears.
I’m confused, is Livekit a standard integration of Openvidu? Because the versions I downloaded from GitHub came with files and commands for configuring Livekit, I’d like to know if it’s really necessary and if there’s any configuration to get around this.
Every first contact with new things can be difficult. Especially with something as complex as real time media. Don’t despair! OpenVidu has been built to make everything as easy as possible.
The best way to start with OpenVidu is running a tutorial. Just choose the frontend framework you feel most comfortable with (vanilla JS, React, Angular, Vue…) and a backend language (Java, Node, PHP…), and go through our guided, step by step tutorial: Application Client Tutorials - openVidu
The tutorial includes running OpenVidu locally, which you can easily do in a Windows, Mac or Linux laptop. Are you having problems running a tutorial against OpenVidu local deployment?
Regarding your question about OpenVidu and LiveKit, we have a page in our documentation stating tihs topic: Comparing OpenVidu - openVidu. OpenVidu is built on top of LiveKit (it is actually a fork of the open-source version of livekit-server). Our main focus is supporting the excellent SDK catalog of LiveKit and its great API, while providing improvements over the open source version of LiveKit and offering deployments that are self-hosted, performant, fault tolerant, scalable and observable. All of this reducing the dev-ops and administration effort (this kind of deployments shouldn’t be restricted to large teams of administrators!). So answering your question: yes, LiveKit’s configuration parameters are compatible with OpenVidu, and we believe that keeping their original name avoids confusion.