Implement LiveKit calls

This commit is contained in:
2026-04-22 23:19:38 +03:00
Unverified
parent b7d884df58
commit 66a1060685
16 changed files with 465 additions and 27 deletions
+5 -2
View File
@@ -4,8 +4,11 @@ import { resolve } from 'path';
const app = express();
const port = process.env.PORT || 3000;
const backendHost = process.env.BACKEND_HOST || "http://localhost:8300";
const fileStorageHost = process.env.FILE_STORAGE_HOST || "http://localhost:8302";
const lan = process.env.LAN_IP;
const backendHost =
process.env.BACKEND_HOST || (lan ? `http://${lan}:8300` : "http://localhost:8300");
const fileStorageHost =
process.env.FILE_STORAGE_HOST || (lan ? `http://${lan}:8302` : "http://localhost:8302");
const filePath = process.env.STATIC_FILE_PATH || ".";
// API proxy middleware
+12
View File
@@ -0,0 +1,12 @@
# Local LiveKit SFU for FromChat development.
# Match keys in deployment/.env — see deployment/livekit.local.env.example
port: 7880
rtc:
tcp_port: 7881
port_range_start: 50000
port_range_end: 60000
use_external_ip: false
keys:
fromchat_dev: "local_dev_secret_must_be_at_least_32_characters_long"
+7
View File
@@ -0,0 +1,7 @@
# Append these lines to deployment/.env so the Python backend can mint LiveKit JWTs.
# Keys must match deployment/livekit.dev.yaml (keys.fromchat_dev).
# LAN_IP = this machines address on your LAN (phones/emulators use it to reach LiveKit).
LAN_IP=192.168.1.14
LIVEKIT_API_KEY=fromchat_dev
LIVEKIT_API_SECRET=local_dev_secret_must_be_at_least_32_characters_long
LIVEKIT_URL=ws://192.168.1.14:7880