How cresscendoll/creamline works
Project type and purpose
• CreamLine is a desktop application built on Electron for real-time screen sharing and streaming.
• It leverages WebRTC for peer-to-peer media transport and includes a built-in signaling server (WebSocket) for connection coordination.
• Primary use case: allow multiple clients to join a default “room-1” and share screens with minimal latency, with auto-update support via electron-updater.
File structure
• Top-level files
• package.json / package-lock.json: dependencies and scripts
• electron-builder.yml: packaging configuration
• config.js: default signaling URL and room settings
• README.md / .gitignore
• Electron app
• main.js: main process entry point (window life cycle, update checks, can launch local signaling server)
• preload.js: sets up context bridge between main and renderer
• renderer.js: UI logic, WebRTC API calls, DOM interactions
• index.html: renderer UI layout
• Signaling server
• signaling-server.js: exports functions to start a WebSocket signaling server
• server.js: CLI entry point for running a standalone signaling server
• Supporting scripts
• run_app.ps1: Windows launch script
Key insights from the README
• Core components: Electron main process, renderer process, standalone or embedded signaling server.
• Dependencies: electron, ws (WebSocket), electron-updater, electron-builder.