How mangtrungzos/realtime-chat-app works
Project type and purpose
• This is a full-stack, real-time video-and-text chat application.
• The client folder is a React+TypeScript SPA that provides chat UI, video streams, and room-management.
• The server folder is a Node.js/TypeScript Socket.IO service for signaling, room lifecycle, and chat message relaying.
• The peerjs folder is a standalone PeerJS signaling server (for WebRTC peer discovery).
File structure
• Top level: three peers of responsibility
• client/ (React frontend)
• server/ (Socket.IO backend)
• peerjs/ (PeerJS signaling server)
• The client uses contexts (ChatContext, RoomContext, UserContext), reducers, and Cypress for e2e tests.
• The server has a minimal folder: src/index.ts and src/room/index.ts for room handling.
• The PeerJS folder contains a Dockerfile to host the PeerJS server in its own container.
• Deployment descriptors: server/fly.toml and Dockerfiles in both server and peerjs.
README
• Tech stack: React, TypeScript, WebSocket (Socket.IO), Node.js, Tailwind CSS, PeerJS.
• Deployed front end on Vercel; server likely on Fly.io; PeerJS via its own container.