尚未偵測到更新。GitHub 發布版本後會顯示在這裡。
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證Privacy-first P2P video calling. WebRTC mesh, local recording via MediaBunny, Bun signaling server. Zero media through any server.
翻譯準備中
取自儲存庫 README
正在載入完整 README。
檢視完整 README ↗Privacy-first peer-to-peer video calling. WebRTC mesh, local recording via MediaBunny. Media stays on the peer connection.
bun install
bun run dev:all
This starts both the Vite dev server (port 3000) and the signaling server (port 8080).
bun run test # unit tests (URL parse, devices, signaling)
bun run typecheck
PeerCall's Playwright suite records video of every test. CI uploads those files as artifacts so you can watch how the product actually behaved at that commit.
bun run build
bunx playwright install chromium
bun run e2e
Recordings land in e2e/recordings/<date>-<sha>/ (gitignored). On GitHub Actions, download the peercall-e2e-<date>-<sha> artifact (90-day retention).
The suite uses fake camera/mic devices. It does not need a real camera.
bun run demo is the optional reliability harness (scripts/demo/repro.ts): it kills the signaling server mid-call. It expects bun run dev on port 3000 and writes screenshots under demo-artifacts/. Prefer bun run e2e for product coverage.
bun run prod
This builds the app and starts the unified production server on port 3000 (configurable via PORT env var).
Favicons, the OG social card, and the web app manifest are generated from source SVGs in public/favicon.svg and scripts/assets/og-image.svg:
bun run generate:assets
Committed assets in public/ are served as-is by the production server.
curl -L https://fly.io/install.sh | shflyctl auth loginflyctl launch --copy-config --name peercall
flyctl deploy
flyctl deploy
flyctl certs add yourdomain.com
Then update your DNS to point to Fly's nameservers.
docker build -t peercall .
docker run -p 3000:3000 \
-e TURN_URLS=turn:your-turn-server:3478 \
-e TURN_USERNAME=user \
-e TURN_CREDENTIAL=secret \
-e CORS_ORIGINS=https://yourdomain.com \
peercall
| Variable | Default | Description |
|---|---|---|
PORT | 3000 | HTTP/WebSocket port |
CORS_ORIGINS | (all) | Comma-separated allowed origins |
METERED_DOMAIN | (none) | Free Open Relay app host, e.g. yourapp.metered.live |
METERED_TURN_API_KEY | (none) | Free Open Relay TURN API key (docs) |
TURN_URLS | (none) | Comma-separated TURN server URLs (alternative to Metered) |
TURN_USERNAME | (none) | TURN username |
TURN_CREDENTIAL | (none) | TURN credential |
WebRTC P2P needs a TURN server for peers behind symmetric NATs or restrictive firewalls — without one, those calls hang on “Connecting…” or never show the other person.
Without TURN configured, PeerCall still serves public STUN servers (many home networks work). For reliable calls, set one of the free options below.
yourappname.metered.live) and TURN API key from the dashboard.flyctl secrets set \
METERED_DOMAIN=yourappname.metered.live \
METERED_TURN_API_KEY=your_api_key
The server fetches short-lived ICE credentials from Metered’s REST API and exposes them on /config (the API key stays server-side).
# Install coturn
sudo apt install coturn
# Configure /etc/turnserver.conf
listening-port=3478
fingerprint
lt-cred-mech
user=peercall:your-secret
realm=peercall.yourdomain.com
# Start
sudo systemctl enable coturn
sudo systemctl start coturn
Then set:
TURN_URLS=turn:peercall.yourdomain.com:3478
TURN_USERNAME=peercall
TURN_CREDENTIAL=your-secret
flyctl secrets set \
TURN_URLS=turn:your-turn-server:3478 \
TURN_USERNAME=user \
TURN_CREDENTIAL=secret
Client (React) ←→ Bun Server (SSR + WebSocket + Static)
↓
Shared signaling protocol
MIT