-
-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add LiveKit as example #48
Conversation
Pull Request Test Coverage Report for Build 3396669949
💛 - Coveralls |
examples/livekit/README.md
Outdated
- deploy the LiveKit server into Kubernetes | ||
- configure STUNner to expose LiveKit to clients | ||
|
||
## Intallation |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
typo
examples/livekit/README.md
Outdated
|
||
## Setup | ||
|
||
The figure below shows how LiveKit is deployed into Kubernetes without the contstraints of running in host network (`hostNetwork: true`). In this setup LiveKit uses STUNner as a 'local' `STUN` and `TURN` server which enhances the security and saves the overhead cost of using public a `STUN` server. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
saves the overhead cost of using public a
STUN server.
Is it a notable overhead?
examples/livekit/README.md
Outdated
|
||
## Installation guide | ||
|
||
Let's start with a disclaimer. The LiveKit client example(browser) must have secure HTTP connection in order to work because, [getUserMedia](https://developer.mozilla.org/en-US/docs/Web/API/MediaDevices/getUserMedia#browser_compatibility) is available only in secure contexts. This induces that the client-server(LiveKit-server) connection must be secure too. According to the [docs](https://docs.livekit.io/deploy/#domain,-ssl-certificates,-and-load-balancer) and our experiences, self-signed certs do not work. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
HTTP -> HTTPS
Self-signed certs works for the getUserMedia, etc... but will not work with secure websocket. So, we should mention that.
This is fantastic, thanks! Couple of minor comments in closing:
|
Finally adding the so-awaited LiveKit demo.
Issuing: #22
Features:
hostNetwork: true
) anymore