You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the README file you state that the user should provide their own signaling server in order not to use the default lio.app signaling server.
This is understandable, but a typical user (e.g. a react-liowebrtc user) may not know how to best do that. Please can you consider providing a link to an existing HOW-TO on the web or similar, or a link to an npm package that can provide server-side signaling functionality?
Thanks,
Sebastian
The text was updated successfully, but these errors were encountered:
To clarify, is the signaling server that works with the liowebrtc library a running instance of the signalmaster service? Or is it an alternative signaling server?
In the README file you state that the user should provide their own signaling server in order not to use the default lio.app signaling server.
This is understandable, but a typical user (e.g. a react-liowebrtc user) may not know how to best do that. Please can you consider providing a link to an existing HOW-TO on the web or similar, or a link to an npm package that can provide server-side signaling functionality?
Thanks,
Sebastian
The text was updated successfully, but these errors were encountered: