Ruby#
This is a minimal server application built for Ruby with Sinatra that allows:
- Generating LiveKit tokens on demand for any application client.
- Receiving LiveKit webhook events.
It internally uses LiveKit Ruby SDK.
Running this application#
Download the tutorial code:
To run this server application, you need Ruby installed on your device.
- Navigate into the server directory
- Install dependencies
- Run the application
Info
You can run any Application Client to test against this server right away.
Understanding the code#
The application is a simple Ruby app using the popular Sinatra web library. It has a single file app.rb
that exports two endpoints:
/token
: generate a token for a given Room name and Participant name./webhook
: receive LiveKit webhook events.
Let's see the code of the app.rb
file:
app.rb | |
---|---|
|
- Import
livekit
library - The port where the application will be listening
- The API key of LiveKit Server
- The API secret of LiveKit Server
- Configure the port
- Enable CORS support
- Set allowed origin (any), methods and headers
- Listen in any available network interface of the host
The app.rb
file imports the required dependencies and loads the necessary environment variables (defined in env.rb
file):
SERVER_PORT
: the port where the application will be listening.LIVEKIT_API_KEY
: the API key of LiveKit Server.LIVEKIT_API_SECRET
: the API secret of LiveKit Server.
Finally the application configures the port, sets the CORS configuration for Sinatra and binds the application to all available network interfaces (0.0.0.0).
Create token endpoint#
The endpoint /token
accepts POST
requests with a payload of type application/json
, containing the following fields:
roomName
: the name of the Room where the user wants to connect.participantName
: the name of the participant that wants to connect to the Room.
app.rb | |
---|---|
|
- A new
AccessToken
is created providing theLIVEKIT_API_KEY
andLIVEKIT_API_SECRET
. - We set participant's identity in the AccessToken.
- We set the video grants in the AccessToken.
roomJoin
allows the user to join a room androom
determines the specific room. Check out all Video Grants. - Finally, we convert the AccessToken to a JWT token and send it back to the client.
The endpoint first obtains the roomName
and participantName
parameters from the request body. If they are not available, it returns a 400
error.
If required fields are available, a new JWT token is created. For that we use the LiveKit Ruby SDK:
- A new
AccessToken
is created providing theLIVEKIT_API_KEY
andLIVEKIT_API_SECRET
. - We set participant's identity in the AccessToken.
- We set the video grants in the AccessToken.
roomJoin
allows the user to join a room androom
determines the specific room. Check out all Video Grants. - Finally, we convert the AccessToken to a JWT token and send it back to the client.
Receive webhook#
The endpoint /webhook
accepts POST
requests with a payload of type application/webhook+json
. This is the endpoint where LiveKit Server will send webhook events.
app.rb | |
---|---|
|
- Get the
Authorization
header from the HTTP request. - Create a new
TokenVerifier
instance providing theLIVEKIT_API_KEY
andLIVEKIT_API_SECRET
. This will validate the webhook event to confirm it is actually coming from our LiveKit Server. - Verify the
Authorization
header with theTokenVerifier
. - Now that we are sure the event is valid, we can parse the request JSON body to get the actual webhook event.
- Consume the event as you whish.
We need to verify that the event is coming from our LiveKit Server. For that we need the Authorization
header from the HTTP request and a TokenVerifier
instance built with the LIVEKIT_API_KEY
and LIVEKIT_API_SECRET
.
If the verification is successful, we can parse the request JSON body and consume the event (in this case, we just log it).
Remember to return a 200
OK response at the end to let LiveKit Server know that the webhook was received correctly.