How aqsakhushi/ibadahconnect works
IbadahConnect is a web platform for arranging Hajj/Umrah Badal and related services: sponsors browse services, authenticate, book and pay, then follow fulfillment; performers and administrators have separate operational workflows. The visible backend exposes authentication, orders, packages, payments, performer, proof, tracking, chat and rules APIs, with MongoDB-backed user, order and package models. The source excerpts do not show most page-to-route calls, so those connections are left out; several backend routes are represented by their exact paths but their internal model wiring is not asserted.
Main entry points: server.js API server · App.jsx Web application · ServiceDetailPage.jsx Service details · auth.js Authentication
Components 26
Web client
- Web application
ibadahconnect/src/App.jsx - Service details
ibadahconnect/src/pages/ServiceDetailPage.jsx - Cart state
ibadahconnect/src/context/CartContext.jsx - Auth interface
ibadahconnect/src/components/AuthModal.jsx - API client
ibadahconnect/src/api.js
Identity and verification
- Authentication
backend/routes/auth.js - User records
backend/models/User.js - Verification email
backend/utils/sendEmail.js
Service and booking
- Package catalog
backend/routes/packages.js - Package records
backend/models/Package.js - Sponsor orders
backend/routes/orders.js - Order records
backend/models/Order.js - Payments
backend/routes/payments.js - Payment review
backend/routes/payment-admin.js
Fulfillment and oversight
- Performer orders
backend/routes/performerOrders.js - Proof and OCR
backend/routes/ocr.js - File uploads
backend/routes/upload.js - Order tracking
backend/routes/track.js - Sponsor performer chat
backend/routes/chat.js - Service rules
backend/routes/rules.js - API server
backend/server.js
Other components
- Sponsor
- Performer
- Administrator
- MongoDB
- SMTP service
Connections 24
- Sponsor → Web application: uses
- Performer → Web application: uses
- Administrator → Web application: uses
- Web application → Service details: routes to
- Web application → Auth interface: renders
- Service details → API client: fetches packages
- Service details → Cart state: adds items
- Auth interface → Authentication: logs in
- API client → API server: requests API
- API server → Authentication: mounts routes
- API server → Package catalog: mounts routes
- API server → Sponsor orders: mounts routes
- API server → Payments: mounts routes
- API server → Payment review: mounts routes
- API server → Performer orders: mounts routes
- API server → Proof and OCR: mounts routes
- API server → File uploads: mounts routes
- API server → Order tracking: mounts routes
- API server → Sponsor performer chat: mounts routes
- API server → Service rules: mounts routes
- API server → MongoDB: connects to
- API server → Package records: seeds packages
- Authentication → Verification email: sends verification
- Verification email → SMTP service: delivers mail