amit2003dh/kisan-setu

Purpose and deployable surfaces

KisanSetu is a multi-role agricultural marketplace: farmers list crops, sellers manage products, buyers purchase, delivery partners fulfill orders, and admins oversee the platform. It has two React single-page clients and one Node/Express backend:

• Customer/role application: frontend/src/index.js, frontend/src/App.js

• Separate admin application: admin/src/index.js, admin/src/App.js

• API and realtime server: backend/server.js, backend/crop-analysis-server.js

Client application and role routing

The main React app owns role-specific dashboards and transactional workflows, using API access and route protection as its client boundary. Its pages cover crop/product listing, carts, orders, payment, delivery, crop analysis, and messaging.

• Application composition: frontend/src/App.js

• Shared authenticated access: frontend/src/components/ProtectedRoute.js

• API client boundary: frontend/src/api/api.js

• Client state for shopping: frontend/src/context/CartContext.js

Marketplace catalog and order lifecycle

The backend exposes resource routes for users, crops, products, carts/orders, tracking, and delivery. MongoDB models represent persistent marketplace state; orders bridge buyer checkout, seller/farmer fulfillment, and delivery assignment/tracking.

• Route layer: backend/routes/cropRoutes.js, backend/routes/productRoutes.js, backend/routes/orderRoutes.js

• Core persisted entities: backend/models/Crop.js, backend/models/Product.js, backend/models/Order.js

• Delivery/tracking domain: backend/routes/deliveryRoutes.js, backend/routes/trackerRoutes.js, backend/models/Delivery.js

Identity, authorization, and administration

JWT-backed authentication protects user and administrative operations. The main UI distinguishes operational roles, while the independently deployed admin app handles user, order, production, delivery-partner verification, and analytics oversight.

• User/auth endpoints: backend/routes/userRoutes.js, backend/models/User.js

• Authorization middleware: backend/middleware/auth.js, backend/middleware/adminAuth.js, backend/middleware/admin.js

• Admin application boundaries: admin/src/api/api.js, admin/src/components/ProtectedRoute.js, admin/src/pages/AdminDashboard.js

• Admin API/domain: backend/routes/adminRoutes.js, backend/models/Admin.js

Realtime communications and location

Socket.io support in the backend enables live negotiation/chat and delivery updates. The customer UI has dedicated buyer/seller/order chat components and a delivery socket hook; map views consume location-oriented delivery state.

• Server realtime entry point: backend/server.js

• Conversation APIs and persistence: backend/routes/chatRoutes.js, backend/models/CustomerChat.js, backend/models/Message.js

• Client realtime/location surfaces: frontend/src/hooks/useDeliverySocket.js, frontend/src/components/LiveMap.js, frontend/src/components/OrderChat.js

AI crop analysis and uploads

Crop disease analysis is a distinct backend capability: image input is accepted from crop-analysis UI flows, handled by analysis routes/services, and integrates Google Gemini. Python model files indicate a parallel/local ML prediction path.

• Gemini and AI routes: backend/routes/geminiRoutes.js, backend/routes/aiRoutes.js

• Alternate analysis implementation: backend/routes/cropAnalysisSimple.js, backend/crop-analysis-server.js

• Python ML assets: backend/ai/cropModel.py, backend/ai/predict.py

• UI entry points: frontend/src/pages/CropDoctor.js, frontend/src/pages/PlantAnalysis.js

Payments, persistence, and external infrastructure

Express runs against MongoDB through its database configuration and Mongoose-style model layer. Razorpay order creation/verification is isolated behind payment routes/configuration. Deployments target Vercel for both React clients and Render/Heroku-compatible hosting for the backend; environment variables supply MongoDB, JWT, Gemini, Razorpay, and Google Maps credentials.

• Database connection: backend/config/db.js, backend/models/index.js

• Payment boundary: backend/routes/paymentRoutes.js, backend/config/razorpay.js

• Checkout UI: frontend/src/pages/Payment.js, frontend/src/pages/payment-status-helper.js