How mightyanubhav/hirebuddy-backend works
Project type and purpose
• It exposes RESTful endpoints for user, buddy, customer, admin, payment, and chatbot interactions.
• It persists data in a database (likely MongoDB or SQL via db/db.js), caches or session data in Redis (db/redis.js), uses Cloudinary for media uploads, and has mailing and real-time socket services.
File structure
• index.js: the application’s entry point where Express is configured and started.
• db/: contains database connection modules (db.js for primary data store, redis.js for caching/session).
• data/: a static JSON file (hirebuddyData.json) used perhaps for seeding or local lookups.
• middlewares/: auth.js (JWT or session auth), roles.js (RBAC enforcement).
• models/: booking.model.js, message.model.js, user.model.js (ORM/ODM schemas).
• routes/: route modules grouped by domain: adminRoutes.js, buddyRoutes.js, customerRoutes.js, chatbotRoute.js, payment.js, userRoutes.js.
• services/: auxiliary layers—editProfilesCloudinary.js (media uploads), mailer.js (SMTP or transactional email), socket.js (WebSocket logic).
• test-clients/: simple scripts simulating buddy and customer API interactions.
README for additional insights
• The README only contains a demo link; architectural details are not documented here.