How adityakamble69/lifeline works
Lifeline is a blood-donor network scaffold: its intended workflow connects donors and people or organizations needing blood, including through donation camps. The present runtime is a Next.js frontend and Express API; the README says they communicate locally, but Supabase is not yet provisioned. The graph preserves the documented domain and the substantial admin capabilities visible in the tree. Relationships between unsampled feature modules are omitted or shown as unverified; the sampled request and profile flows have clearer routing and service evidence.
Main entry points: index.js API route registry · auth.service.js Identity sync · adminRequests.routes.js Request admin routes · me.controller.js Profile API
Components 23
Web experience
- Web application
frontend/src/app - Donor portal
frontend/src/app/dashboard - Public discovery
frontend/src/app/camps - Admin console
frontend/src/app/admin
API and identity
- Express API
backend/src/server.js - API route registry
backend/src/routes/index.js - Authentication
backend/src/middleware/requireAuth.js - Identity sync
backend/src/services/auth.service.js - User records
backend/src/repositories/user.repository.js
Donor services
- Profile API
backend/src/controllers/me.controller.js - Profile services
backend/src/services/me.service.js - Profile data access
backend/src/repositories/me.repository.js - Camp discovery and signup
frontend/src/app/dashboard/camps - Blood requests
backend/src/routes/requests.routes.js
Organization admin
- Request admin routes
backend/src/routes/adminRequests.routes.js - Request review
backend/src/controllers/adminRequests.controller.js - Request workflows
backend/src/services/adminRequests.service.js - Request data access
backend/src/repositories/adminRequests.repository.js - Admin operations
backend/src/controllers - Data export
backend/src/repositories/adminExport.repository.js
Other components
- Donors and requesters
- Clerk identity
- Supabase database
Connections 21
- Donors and requesters → Web application: use
README.md - Web application → Express API: calls health endpoint
README.md - Express API → API route registry: mounts API routes
backend/src/server.js - API route registry → Blood requests: registers routes
backend/src/routes/index.js - API route registry → Request admin routes: registers routes
backend/src/routes/index.js - Request admin routes → Authentication: guards requests
backend/src/routes/adminRequests.routes.js - Request admin routes → Request review: dispatches
backend/src/routes/adminRequests.routes.js - Request review → Request workflows: calls
backend/src/controllers/adminRequests.controller.js - Request workflows → Request data access: uses
backend/src/services/adminRequests.service.js - Authentication → Identity sync: synchronizes user
backend/src/middleware/requireAuth.js - Identity sync → Clerk identity: fetches identity
backend/src/services/auth.service.js - Identity sync → User records: finds or inserts
backend/src/services/auth.service.js - User records → Supabase database: reads and writes
backend/src/repositories/user.repository.js - API route registry → Profile API: registers profile routes
backend/src/routes/index.js - Profile API → Profile services: calls
backend/src/controllers/me.controller.js - Profile services → Profile data access: uses
backend/src/services/me.service.js - Donor portal → Profile API: uses profile endpoints
- Donor portal → Camp discovery and signup: offers camp signup
- Public discovery → Blood requests: supports request discovery
- Admin console → Admin operations: manages operations
- Admin console → Data export: requests exports