live-message/chat

Purpose and deployment shape

Life Message is a registration-free, temporary room-based chat with browser calling support. The checked-in application surface is primarily static HTML/CSS/JavaScript under web/; deployment is container-oriented via Dockerfile, docker-compose.yml, and nginx.conf. The README describes a Flask/Flask-SocketIO backend, but its app.py and dependency manifest are not present in this tree.

Browser entry and route selection

web/index.html is the browser entry point. Route-to-page mapping is centralized in web/routes.json, with primary views at web/pages/home.html and web/pages/chat.html. The home flow creates or joins a room; the chat page is the active room workspace.

Room lifecycle and sharing

Room management UI is split into reusable menu fragments: web/menus/create-chat.html, web/menus/edit-chat.html, and web/menus/delete-chat.html. Sharing a generated room URL is handled by web/static/scripts/share.js. The intended room identifier model is UUID-based and temporary, per the README; backend ownership of generation, expiry, and deletion is an important boundary not represented in the supplied tree.

Real-time chat and calling transport

Chat orchestration is centered on web/static/scripts/chat/chat.js, with socket lifecycle/event handling in web/static/scripts/chat/websocket.js and presentation behavior in web/static/scripts/chat/ui.js. The client is expected to connect to a Flask-SocketIO/WebSocket service for messages and room events. WebRTC calling is described in the README; signaling would logically traverse this socket layer, while peer media/data traffic bypasses the application server after negotiation.

Client-side identity and local state

Anonymous participant behavior is managed by web/static/scripts/chat/users.js and web/static/scripts/user/login.js. Client persistence/data access is isolated in web/static/scripts/database/db.js, with contact-specific operations in web/static/scripts/database/contacts.js. This separates local browser state from authoritative room membership and message delivery, which must remain server-side for multi-user synchronization.

UI composition and progressive installation

Chat-specific styling and interaction assets live in web/static/css/chat.css and web/static/scripts/chat/. Shared shell styling is in web/static/css/main.css. The project includes a web-app manifest at web/static/manifest.json and installation logic at web/static/scripts/install-app.js, indicating Progressive Web App-oriented browser installation support.

Infrastructure and external boundaries

Nginx configuration in nginx.conf is the likely HTTP/static-file and reverse-proxy boundary, with docker-compose.yml defining local multi-container composition. Dockerfile packages the deployable runtime. Material external/browser services are WebSocket transport (Flask-SocketIO backend), WebRTC peer connections, and browser storage/PWA APIs; HTTPS is required operationally for secure transport and typical WebRTC deployment.