📎 Webclip
Create a Video Party App With Rails Part 1: Building the Backend
The post describes the backend for a Rails video watch party app built with the Vonage Video API. It sets up a landing page, a party video chat view, and a watch-party screenshare view, with password gating and moderator-only watch mode control.
Reading notes#
- The app uses Ruby on Rails 6+ and the Vonage Video API, with PostgreSQL and environment variables managed through dotenv-rails.
- A
Sessionmodel stores the current video session ID and marks sessions as expired or active. - The model can create a new Vonage session, load the last active session, and generate participant tokens.
- Moderator access is handled by generating a token with moderator role when the user name matches the configured moderator name.
- Routes map the landing page, party view, screenshare view, name submission, and chat submission to
VideoControlleractions. - The controller loads API credentials, the session ID, the moderator name, and the participant token before each action.
- The
nameaction checks the submitted password againstPARTY_PASSWORDand redirects to the party page only when it matches. - A
site_info.ymlfile centralizes language, layout text, navbar text, and chat labels used across the views. ApplicationControllerreads the YAML config and exposes it through instance variables for the views.- The shared layout sets the HTML language and direction, loads the OpenTok JavaScript library, and passes Ruby variables into JavaScript.
- The header partial shows the app title, participant count placeholder, and the Watch Mode button.
- The chat partial includes a history container and a form that posts messages to
/chat/send. - The landing page asks for name and party password and displays flash errors for incorrect passwords.
- The party view passes token, name, and moderator name to JavaScript, then renders placeholders for publisher, subscribers, chat, and the chat toggle button.
- The screenshare view uses similar JavaScript setup and renders placeholders for screenshare video, audio, chat, and the chat toggle button.
- The article ends by noting that the backend is ready and the frontend will be built in Part 2.
