How zoom/meetingsdk-headless-linux-sample works
Project Type and Purpose
• The README makes it clear that this is a sample bot for the Zoom Meeting SDK on Linux. It’s built to run inside a Docker container, and it uses a configuration file (config.toml) or command line arguments to set up details such as Zoom credentials, meeting parameters, and potentially integrations with external services (e.g., AssemblyAI, Anthropic).
• The project integrates with the Zoom SDK (found in the lib/zoomsdk folder) and handles multiple kinds of events (authentication, meeting events, recording control, reminders).
File Structure
• Top-Level Files: Files like Dockerfile, compose.yaml, CMakeLists.txt, and sample.config.toml indicate how the project is built, deployed, and configured.
• bin/entry.sh: This is the entry point script that likely sets up environment variables or triggers the main executable.
• src/ Directory: Contains the bulk of the core logic.
• Main application (src/main.cpp) serves as the application’s entry point.
• src/Config.* files handle configuration management.
• src/Zoom.* wraps or interacts with the Zoom SDK functionality.
• src/events: Contains a set of event classes (for authentication, meeting service, recording, and reminders) that form the event-handling backbone of the application.
• src/raw_record and src/raw_send: Likely manage handling of raw audio data and video sources, interfacing directly with lower-level API callbacks from Zoom.
• src/util: Provides supporting utilities like logging, a Singleton helper, and a SocketServer for inter-component communication.
• lib/zoomsdk: Contains the Zoom SDK library (it’s a placeholder directory where you load the actual SDK).