sanjaygoud009/pawmira

Purpose and Entry Points

PawMira is a MERN rescue-operations system for reporting injured animals, triaging cases, and enabling NGO response. The browser application starts at client/src/main.jsx and composes UI/routing from client/src/App.jsx. The Express API starts at server/server.js, connects through server/config/db.js, and exposes domain route modules.

Client Application and User Flows

React provides public information, authentication, emergency reporting, rescue feed, lost/found, volunteer, and NGO/admin experiences. Key operational pages are client/src/pages/ReportEmergency.jsx, client/src/pages/Dashboard.jsx, and client/src/pages/AdminDashboard.jsx. Shared report UI covers photo intake, location selection, and report presentation in client/src/components/report/ImageUpload.jsx, client/src/components/report/LocationPicker.jsx, and client/src/components/report/RescueCard.jsx.

Identity and Authorization Boundary

Client auth state is centralized in client/src/context/AuthContext.jsx, with consumer access through client/src/hooks/useAuth.js. Backend JWT authentication and access control are enforced by server/middleware/auth.js; identity persistence is modeled in server/models/User.js. Auth lifecycle endpoints are defined by server/routes/auth.js and implemented in server/controllers/authController.js.

Rescue Report Lifecycle

Reports enter from the web reporting flow or WhatsApp integration, pass through route/controller handling, and persist as rescue records. The core API boundary is server/routes/reports.js → server/controllers/reportController.js → server/models/Report.js. The Report model supports soft deletion, priority/status history, and geospatial location queries; dashboard/feed consumers retrieve and act on this operational queue.

Media and Location Processing

Images are compressed before submission in client/src/utils/imageCompressor.js, then validated and accepted by upload middleware in server/middleware/upload.js. Cloudinary integration is configured in server/config/cloudinary.js; image validation resides in server/utils/imageValidator.js. Location selected client-side is stored in MongoDB report data, whose geospatial indexing supports proximity/filtering for responders.

Messaging, Notifications, and WhatsApp Intake

In-app rescue conversations use server/routes/rescueMessageRoutes.js, server/controllers/rescueMessageController.js, and server/models/RescueMessage.js; broader messaging has a separate messagesRoutes domain. Notifications are independently exposed through server/routes/notifications.js and persisted in server/models/Notification.js. Twilio WhatsApp webhook/chatbot flow is isolated in server/routes/whatsapp.js and server/controllers/whatsappController.js, with temporary conversational state in TTL-backed server/models/WhatsAppSession.js.

Supporting Operational Domains and Runtime

Lost/found animal records are a separate workflow from emergency reports, centered on server/routes/lostFound.js, server/controllers/lostFoundController.js, and server/models/LostPet.js/server/models/FoundPet.js. Admin operations, rankings/gamification, contact handling, escalations, cleanup, and email are backend service domains. Runtime infrastructure is Node/Express, MongoDB/Mongoose, Cloudinary, and Twilio; client deployment configuration is present at client/vercel.json, with PWA/offline assets in client/public/sw.js.