How delt4d/echo works
Project type and purpose
• Echo is a full-stack session-recording and replay system.
• Purpose: capture real-time user interactions in a web page (Recorder), send them to a server (SignalR), store them, and replay them visually (Mimic).
File structure
• Top level:
• Docs, Echo.run (run/profiles), docker files, compose, .NET solution.
• Lib/Client: shared client library (recorder, mimic, data, handlers).
• Lib/Server: shared .NET library (EchoLib) and models.
• Preview/Client: standalone React/Vue/vanilla preview web app for recorder & mimic.
• Preview/Server: ASP.NET Core SignalR server with EchoHub and controllers.
• Patterns:
• Client–Server via SignalR (WebSocket).
• Shared libraries separate concerns: client-side logic, server-side logic.
• DevOps:
• Back.Dockerfile and Front.Dockerfile for containerizing preview server and client.
• docker-compose.yml wires up both containers for local testing.
README for additional insights
• Real-time recording pipeline and replay pipeline are described.
• No persistent database is mentioned—assume file or in-memory store via EchoLib (extendable).
• Tech stack:
• Frontend: vanilla JS/NPM + custom elements, Rollup build, preview uses standard web stack (HTML/CSS/JS).
• Backend: ASP.NET Core, SignalR hub, C# shared library.