A self-hosted meeting service built on the Live777 WebRTC engine (WHIP/WHEP).
- Node.js 26 and npm
- Stable Rust with rustfmt and Clippy
- Live777/Liveion on port 7777
- Docker for the default Liveion service and container builds
Start Liveion:
docker compose up -dGenerate a secret once and keep it stable across restarts. Existing user tokens and room ownership depend on it.
export SECRET="$(openssl rand -hex 32)"
npm ci
npm run build
cargo runcargo run serves the production WebApp and API on http://localhost:4000. The initial npm run build creates static/dist, which is required when compiling the backend.
For frontend development, run Vite in another terminal:
npm run devVite listens on http://localhost:5173 and proxies the API, browser logs, WHIP/WHEP and session signaling through the Rust server on port 4000.
| Variable | Default | Purpose |
|---|---|---|
SECRET |
required | HS512 signing secret; at least 32 bytes, not a known default |
PORT |
4000 |
WOOM HTTP port |
LIVE777_URL |
http://localhost:7777 |
Upstream Live777/Liveion URL |
LIVE777_TOKEN |
empty | Optional upstream bearer token |
DATA_FILE |
./data/woom.json |
Durable state file; :memory: disables persistence for tests |
LOG_READ_TOKEN |
empty | Optional admin token for reading browser diagnostics; at least 32 bytes when set |
WOOM requires membership authorization for room events, chat, presence and media signaling. Room passwords and secrets are never included in API responses or startup logs.
The browser reports errors, warnings and WebRTC lifecycle events to WOOM. Set a separate admin token to enable the diagnostic export endpoint:
export LOG_READ_TOKEN="$(openssl rand -hex 32)"
curl -H "Authorization: Bearer $LOG_READ_TOKEN" \
"http://localhost:4000/log?meetingId=123-456-789&limit=500" \
-o woom-browser-log.ndjsonFilters include meetingId, sessionId, level, since (epoch milliseconds) and limit. The NDJSON output contains session and meeting identifiers, timestamps, event data, page URL and user agent, so it can be supplied directly to an AI assistant for troubleshooting.
GET /log is disabled when LOG_READ_TOKEN is unset and never accepts an ordinary user JWT. The in-memory buffer retains the most recent 5000 entries and is cleared on restart; long-term history remains available through the existing client_log service-log output. Exported data is redacted, but should still be treated as sensitive diagnostic material.
Rooms, meetings, participants, chat and meeting records are stored in an atomically replaced JSON file. Presence is ephemeral and is restored by client heartbeats after a restart.
The JSON store supports one WOOM process only. Do not share one file between replicas. Back up DATA_FILE and the configured SECRET together. A damaged or unknown-version data file prevents startup rather than being overwritten.
For Docker, /data/woom.json is the default and /data should be a persistent volume:
docker build -t woom .
docker volume create woom-data
docker run --rm --network woom -p 4000:4000 \
-e SECRET \
-e LIVE777_URL=http://live777:7777 \
-e LOG_READ_TOKEN \
-v woom-data:/data \
woomOnly HTTP signaling is proxied through WOOM. WebRTC media still requires reachable ICE candidates. On NAT, Docker Desktop or public deployments, configure Live777's external candidates and UDP/TURN networking as appropriate; publishing only TCP port 7777 is not a general NAT solution.
For Fly.io, create the volume once in the configured region, set the secrets, then deploy:
fly volumes create woom_data --region nrt --size 1
fly secrets set SECRET="$(openssl rand -hex 32)"
fly secrets set LOG_READ_TOKEN="$(openssl rand -hex 32)"
fly secrets set LIVE777_TOKEN="your-upstream-token" # if required
fly deploymake
export SECRET="your-stable-production-secret"
./target/release/woommake builds the WebApp before compiling the release binary. Cargo and npm both use their lockfiles in release and container builds.
Format and lint the WebApp and E2E sources with Biome 2.6.4, ESLint and vue-tsc:
npm run format
npm run lintRust format, lint and unit/API/store tests:
npm run test:rustBrowser E2E tests use Chromium with fake media devices:
docker compose up -d
npx playwright install chromium
npm run test:e2eThe E2E server uses a test-only secret and in-memory storage. By default, Playwright starts the newly built binary rather than reusing whatever is already listening on port 4000. For an explicitly verified running server, opt in with:
E2E_REUSE_SERVER=true npx playwright testThe suite covers meeting and chat flows, authorization boundaries, media lifecycle, reconnect/recovery, video frame progress and PWA offline behavior.