How sharif-minhaz/mediaid works
Project type and purpose
• This is a full-stack web application (“MediAid”) whose goal is to let individuals and organizations donate unused or unexpired medicines and let receivers apply to receive them.
• The client is a React/Vite single-page application, the server is a Node.js/Express REST API, data is stored in MongoDB, and images are managed via Cloudinary.
File structure
• Top-level directories:
– client: React front-end (features folder with Redux slices, components, pages, routers, utils).
– server: Express back-end (controllers, routes, models, middlewares, utils, DB connection).
– template: static HTML/CSS templates (used for initial design or email templates).
• Config files:
– client/default.env & server/default.env for environment variables.
– vite.config.js, package.json in each to manage builds.
• Architectural patterns:
– Front-end: feature-based folder grouping + Redux Toolkit + React Router.
– Back-end: MVC pattern (models/controllers/routes) + middleware chain (auth, error handler, file upload).
README for additional insights
• Confirms usage of JWT for authentication (admin credentials given).
• Mentions donation workflow, file uploads (images/documents), admin approval process.
a. Main components
1. Browser / React SPA
2. Vite Dev Server (development)
3. Express API Server
4. MongoDB database
5. Cloudinary (image storage)
6. Optional: Static template host (serves template folder or email templates)
b. Relationships & interactions
– Browser sends HTTP/HTTPS requests (API calls) to the Express server.
– Server authenticates using JWT middleware, then routes requests to appropriate controllers.
– Controllers use Mongoose models to read/write data in MongoDB.
– For image/document uploads, server’s upload utility sends files to Cloudinary, stores URLs in MongoDB.
– Static template files are served either by Express or from a CDN.
c. Architectural patterns and design principles
– MVC on the server side.
– Feature slices + Redux Toolkit on the client side.
– RESTful API endpoints grouped by resource (auth, medicines, gallery, etc.).
– Separation of concerns: routing, business logic (controllers), data layer (models), middleware.
d. Key technologies
– Front-end: React, Vite, Redux Toolkit, React Router, Axios/fetch.
– Back-end: Node.js, Express, Mongoose, JWT, Cloudinary SDK, Multer.
– Database: MongoDB (Atlas or local).
– DevOps: dotenv files, .env, environment variables, CORS, error handling.