feat: add jitsi meet self-hosted video platform integration #600
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add platform column to rooms and meetings database tables with Literal typing to support multiple video conferencing platforms (whereby, jitsi). - Add platform column to rooms/meetings SQLAlchemy tables with whereby default - Update Room/Meeting Pydantic models with platform field and Literal typing - Modify RoomController.add() to accept platform parameter - Update MeetingController.create() to copy platform from room 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <[email protected]>
Generate Alembic migration to add platform column to rooms and meetings tables enabling multi-platform video conferencing support. - Add platform column to meeting table with whereby default - Add platform column to room table with whereby default - Migration tested successfully with alembic upgrade head 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <[email protected]>
Add comprehensive Jitsi Meet configuration settings to settings.py following the same pattern as WHEREBY settings. - Add JITSI_DOMAIN with meet.jit.si default - Add JITSI_JWT_SECRET for JWT token signing - Add JITSI_WEBHOOK_SECRET for webhook validation - Add JITSI_APP_ID, JITSI_JWT_ISSUER, JITSI_JWT_AUDIENCE for JWT configuration - Follow consistent naming and typing patterns 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <[email protected]>
Create complete video platforms abstraction layer following daily.co branch pattern with Jitsi-specific directory structure. - Add video_platforms base module with abstract classes - Create VideoPlatformClient, MeetingData, VideoPlatformConfig interfaces - Add platform registry system for client management - Create factory pattern for platform client creation - Add Jitsi directory structure with __init__.py, tasks.py, client.py - Configure Jitsi platform in factory with JWT-based authentication 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <[email protected]>
Complete implementation of JitsiClient following VideoPlatformClient interface with JWT-based room access control and webhook signature verification. - Add JWT token generation with proper payload structure - Implement unique room name generation with timestamp - Create separate user/host JWT tokens with moderator permissions - Build secure room URLs with embedded JWT parameters - Add HMAC-SHA256 webhook signature verification for Prosody events - Implement all abstract methods with Jitsi-specific behavior - Include comprehensive typing and error handling 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <[email protected]>
- Added JitsiClient registration to platform registry - Enables dynamic platform selection through factory pattern - Factory configuration already supports Jitsi settings - Platform abstraction layer now supports beide Whereby and Jitsi 🤖 Generated with Claude Code
- Added comprehensive Jitsi webhook endpoint in views/jitsi.py - Handles Prosody event-sync events (muc-occupant-joined/left) - Implements participant counting following whereby.py pattern - Added Jibri recording completion webhook endpoint - Includes signature verification with fallback when platform client unavailable - Registered router in app.py for /v1/jitsi endpoints - Added health check endpoint for webhook configuration 🤖 Generated with Claude Code
- Added platform field to Room, CreateRoom, and UpdateRoom models - Updated rooms_create function to pass platform parameter - Rewrote rooms_create_meeting to use platform factory pattern - Added graceful fallback to legacy whereby implementation - Maintained API compatibility and error handling patterns - Prepared for multi-platform support (Whereby/Jitsi) 🤖 Generated with Claude Code
- Added complete end-user configuration guide at server/platform-jitsi.md - Covers prerequisites, environment setup, and Jitsi Meet configuration - Includes JWT authentication, Jibri recording, and Prosody event-sync setup - Provides troubleshooting guide with common issues and solutions - Documents security best practices and performance optimization - Includes testing procedures and migration guidance from Whereby - Ready for production deployment with step-by-step instructions - Uses environment variable placeholders for security 🤖 Generated with Claude Code
- Added PyJWT>=2.8.0 to pyproject.toml dependencies - Installed dependency via uv sync successfully - Verified JWT generation functionality works correctly - Confirmed platform factory creates JitsiClient instances - Validated database migrations applied (platform fields available) - Tested webhook endpoints are registered and functional - Verified FastAPI app starts without errors with full integration - All integration tests pass - Jitsi platform fully functional 🤖 Generated with Claude Code
- Created complete test coverage for video platform abstraction - Tests for base classes, JitsiClient implementation, and platform registry - JWT generation tests with proper mocking and error scenarios - Webhook signature verification tests (valid/invalid/missing secret) - Platform factory tests for Jitsi and Whereby configuration - Registry tests for platform registration and client creation - Webhook endpoint tests with signature verification and error cases - Integration tests for rooms endpoint with platform abstraction - 24 comprehensive test cases covering all video platform functionality - All tests passing with proper mocking and isolation 🤖 Generated with Claude Code
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
- Complete end-user configuration guide for Whereby video platform - Covers account setup, API key generation, and webhook configuration - AWS S3 storage setup with IAM permissions and security best practices - Room creation, recording options, and meeting feature configuration - Troubleshooting guide with common issues and debug commands - Security considerations and performance optimization tips - Migration guidance from other platforms 🤖 Generated with Claude Code
- Complete end-user configuration guide for self-hosted Jitsi Meet - Covers installation, JWT authentication, and Prosody configuration - Webhook event handling with mod_event_sync setup - Jibri recording service configuration and finalize script - Room creation, JWT token management, and security best practices - Comprehensive troubleshooting with debug commands and solutions - Performance optimization and scaling considerations - Migration guidance from Whereby platform 🤖 Generated with Claude Code
- Create VideoPlatform StrEnum with WHEREBY and JITSI values - Update rooms.py and meetings.py to use VideoPlatform enum - Update views/rooms.py and video_platforms/factory.py to use enum values - Generate new migration with proper server_default='whereby' - Apply migration successfully with backward compatibility - Fix linting and formatting issues Addresses PR feedback point 1: use StrEnum instead of Literal[]
- Create video_platforms/whereby/ directory with __init__.py, client.py, tasks.py - Implement WherebyClient inheriting from VideoPlatformClient interface - Move all functions from whereby.py into WherebyClient methods - Use VideoPlatform.WHEREBY enum for PLATFORM_NAME - Register WherebyClient in platform registry - Update factory.py to include S3 bucket config for whereby - Update worker process to use platform abstraction for get_room_sessions - Preserve exact API behavior for meeting activity detection - Maintain AWS S3 configuration handling in WherebyClient - Fix linting and formatting issues Addresses PR feedback point 7: implement video_platforms/whereby structure Note: whereby.py kept for legacy fallback until task 7 cleanup
- Remove 'transcription': True from JWT features in _generate_jwt - Replace int(time.time()) with generate_uuid4() for room naming to avoid conflicts - Replace datetime.utcnow() with datetime.now(tz=timezone.utc) for proper timezone handling - Create JitsiMeetingData(MeetingData) class with typed extra_data properties - Update PLATFORM_NAME = VideoPlatform.JITSI to use enum - Update create_meeting to return JitsiMeetingData instance with proper typing - Fix get_room_sessions mock to use timezone-aware datetime - Export JitsiMeetingData from jitsi module Addresses PR feedback points 4, 5, 6, 10: remove transcription features, use UUID, proper datetime handling, and typed meeting data
- Add events column as JSON type to meetings table with default empty array - Add events: List[Dict[str, Any]] field to Meeting model - Create migration 2890b5104577 for events column and apply successfully - Add MeetingController helper methods for event storage: - add_event() for generic event storage with timestamps - participant_joined(), participant_left() for participant tracking - recording_started(), recording_stopped() for recording events - get_events() for event retrieval - Update Jitsi webhook endpoints to store events: - Store participant join/leave events with data and timestamps - Store recording start/stop events from Prosody webhooks - Store recording completion events from Jibri finalize script - Events stored with type, timestamp, and data for webhook history tracking - Fix linting and formatting issues Addresses PR feedback point 12: save webhook events in meetings events field
- Add typing overloads to get_platform_client for JitsiClient and WherebyClient return types - Add overloads to create_platform_client in factory for better IDE support - Remove PyJWT fallback imports from views/rooms.py - Remove platform defaults from CreateRoom and UpdateRoom models - Clean up legacy whereby fallback code in meeting creation - Use direct platform client access instead of conditional fallbacks 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <[email protected]>
- Move Jitsi router from views/jitsi.py to video_platforms/jitsi/router.py - Move Whereby router from views/whereby.py to video_platforms/whereby/router.py - Update __init__.py files to export routers from platform packages - Update app.py imports to use video_platforms instead of views - Remove old view files after successful migration - Maintain exact same API endpoint paths (/v1/jitsi, /v1/whereby) 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <[email protected]>
- Remove excessive inline comments from meeting creation flow - Remove verbose docstrings from simple property methods and basic functions - Clean up obvious comments like 'Generate JWT tokens', 'Build room URLs' - Remove unnecessary explanatory comments in platform clients - Keep only essential documentation for complex logic - Simplify race condition handling comments - Remove excessive method documentation for simple operations 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <[email protected]>
- Add comprehensive webhook event storage documentation - Document event structure and JSON storage in meetings table - Add practical webhook testing examples with proper signature generation - Include detailed troubleshooting for webhook signature verification issues - Add webhook event payload examples for all supported event types - Document event storage verification and database querying methods - Enhance existing webhook configuration with real-world examples 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <[email protected]>
- Update existing tests for StrEnum instead of string literals - Add comprehensive WherebyClient tests with HTTP mocking - Add webhook event storage tests for participant and recording events - Add typing overload tests for create_platform_client factory - Update webhook test paths to new video_platforms router locations - Fix mock ordering and parameter issues in async tests - Test all platform client functionality including signature verification - Verify webhook event storage with proper timestamp handling 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <[email protected]>
…Jitsi health check
tito
changed the title
- Add NEXT_PUBLIC_VIDEO_PLATFORM environment variable support - Create video platform abstraction layer with factory pattern - Implement Whereby and Jitsi platform providers - Update room meeting page to use platform-agnostic component - Add platform display in room management (cards and table views) - Support single platform per deployment configuration - Maintain backward compatibility with existing Whereby integration 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <[email protected]>
- Resolved conflicts in server/reflector/views/rooms.py to keep platform-agnostic approach - Resolved conflicts in www/app/[roomName]/page.tsx to keep VideoPlatformEmbed approach - Accepted main's version of generated API files (schemas.gen.ts, services.gen.ts, types.gen.ts) - Removed config-template.ts as per main branch changes
tito
changed the title
tito
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
TBD