Architecture and compatibility
Browser ──HTTPS──> Proxy ──> Node.js (port 3000) │ ├─ Next.js: pages and interface │ ├─ Socket.IO: signalling, encrypted chat relay │ └─ mediasoup: one SFU router per room └───── UDP/TCP 10000-10100 (DTLS-SRTP) ──────┘A single Node.js process serves the interface, the signalling and the SFU. Each room has its own mediasoup router; an empty room is closed. State (rooms, connected people) lives in memory: a restart drops ongoing calls.
Project tree
Section titled “Project tree”militant-visio/├── app/ Next.js pages (home, room /room/[id])├── components/ Interface: VideoRoom (room), UI components├── hooks/ React hooks (notifications)├── lib/ crypto.ts (chat encryption), i18n.tsx (4 languages), utils├── server/index.js HTTP, Socket.IO and mediasoup server├── public/ Logo, icons, manifest, version.txt├── scripts/test/ Automated tests (npm test)├── docker/ Dockerfile, docker-compose.yml, example nginx.conf├── docs/ README translations, badges├── Makefile Deployment and publishing commands├── .env.example Configuration template└── VERSION Published versionCompatibility
Section titled “Compatibility”Browsers
Section titled “Browsers”| Browser | Video call | Screen sharing | Note |
|---|---|---|---|
| Firefox (recent) | ✓ | ✓ | |
| Chromium, Chrome, Brave, Edge (recent) | ✓ | ✓ | |
| Safari (macOS, recent) | ✓ | ✓ | |
| Safari iOS / iPadOS | ✓ | ✕ | Mobile browsers do not offer screen sharing. |
| Android (Chrome, Firefox) | ✓ | ✕ | Same limitation. |
Technical stack
Section titled “Technical stack”| Component | Version |
|---|---|
| Node.js | 22 in the Docker image; 20 or later locally |
| Next.js | 16 |
| React | 18 |
| mediasoup / mediasoup-client | 3 |
| Socket.IO | 4 |
| Image | Debian Bookworm slim, linux/amd64 |