How pavantech01/ashokafae works
Project type and purpose
• This is a full-stack event management application (“Event Management Application For Ashokafae”) with:
• A React-based client (“client-ashokafae”) hosting UI pages for browsing events, user auth, blog posts, contact form, etc.
• A Node.js/Express REST API server (“server-ashokafae”) handling user management, event CRUD, payments, file uploads, notifications.
• Integration with external services: Cloudinary (image/media storage), Firebase (auth or notifications), Razorpay (payment gateway).
• A database (configured in server/config/db.config.js, likely MongoDB).
File structure
• Top-level split:
• client-ashokafae/ – React app (CRA structure + TailwindCSS).
• server-ashokafae/ – Express application with MVC + service layers + middleware + utils + tests.
• Frontend:
• public/ + src/ with components/, pages/, utils/api.js, AuthContext.
• Post-CSS/Tailwind config for styling.
• Backend:
• src/config/ – external service credentials (Cloudinary, Firebase, Razorpay, DB).
• src/routes/ → src/controllers/ → src/services/ → src/models/ (standard layered pattern).
• src/middleware/ for auth, role-based access, validation, error handling, file upload.
• src/utils/ for error wrappers and validators.
• src/tests/ for unit tests.
Key README insights
• It describes install/run steps for both client and server.
Detail
• Critical pieces: AuthContext in the client, upload.middleware, role.middleware on server, routes for events/payments/users.
• Do not over-compartmentalize—group similar middleware or services if needed.