How sankalp51/chatify works
Project type and purpose
• Chatify is a full-stack, real-time chat application built on the MERN stack (MongoDB, Express.js, React.js, Node.js) with Socket.io for bidirectional messaging.
• Core use cases: user sign-up/login, one-to-one or group chat, emoji support, password reset via email/OTP, file/image uploads, theme toggle.
File structure
• Top-level split:
• frontend/ (React + Vite + Tailwind + Redux + Socket.io client)
• backend/ (Node.js + Express + Socket.io server + Mongoose + Redis + Cloudinary + Nodemailer)
• backend layers:
• config/ – 3rd-party setup (DB, Redis, CORS, Multer, Cloudinary, Nodemailer)
• controllers/ – MVC controllers (auth, chat, message, user, password reset)
• middlewares/ – credential checks, JWT verification, error handling
• models/ – Mongoose schemas (User, Chat, Message)
• routes/ – Express routers for REST endpoints
• utils/ – OTP generation/email templating
• views/public/ – static HTML/CSS (404, index)
• frontend layers:
• src/components/ – UI components (base_components & shadcn/ui)
• src/context & redux/features – global state (auth, chats, notifications)
• src/hooks – custom hooks (Axios instance, auth, theme, refresh tokens)
• src/pages & layouts – top-level pages (Auth, Home, ResetPassword) + route wrappers
• src/socket.ts – Socket.io client initialization
• src/utils/lib – helper functions (chat logic, axios config)
README insights
• Explicit list of tech stack
• Emphasis on real-time messaging via Socket.io
• JWT for auth, Redis for caching/session, Cloudinary for media, Multer for uploads, Nodemailer for emails
Detail without over-splitting
• Every major module: UI, state, API, real-time, DB, cache, media, email
• Data flows (REST vs WebSocket) are clearly differentiated and labeled