How nivin-sithija/hotel-skynest works
SkyNest is a role-based hotel management system for guests, receptionists, and administrators. Users sign in and access role-specific dashboards and hotel workflows; frontend pages call a REST API, which exposes authentication and operational endpoints backed by MySQL. The major product areas include bookings and rooms, guest and service management, payments and live billing, financial configuration, support, and reporting. The graph follows documented routes and sampled imports; several domain implementations are represented at their existing directories because their source was not excerpted.
Main entry points: server.js API server · database.js MySQL database · api.js API client · App.jsx Role-based app
Components 20
Web experience
- Role-based app
frontend/src/App.jsx - Auth context
frontend/src/context/AuthContext.jsx - API client
frontend/src/utils/api.js - Booking pages
frontend/src/pages - Role dashboards
frontend/src/pages/dashboards - Service workflows
frontend/src/pages/ServiceRequests.jsx - Finance pages
frontend/src/pages/PaymentGateway.jsx - Reporting page
frontend/src/pages/Reports.jsx
API and access
- API server
backend/server.js - Auth routes
backend/routes/authRoutes.js - JWT access
backend/middleware/auth.js - Authentication
backend/controllers/authController.js
Hotel operations
- Booking and rooms
backend/controllers/bookingController.js - Guest management
backend/controllers/guestController.js - Service requests
backend/controllers/serviceRequestController.js
Finance and insights
- Payment processing
backend/controllers/paymentController.js - Fees and tax rules
backend/controllers/taxDiscountController.js - Business reports
backend/controllers/reportController.js
Persistence
- MySQL database
backend/config/database.js
Other components
- Hotel user
Connections 26
- Hotel user → Role-based app: uses
- Role-based app → Auth context: provides auth
frontend/src/App.jsx - Role-based app → Role dashboards: routes to
frontend/src/App.jsx - Role-based app → Booking pages: routes to
frontend/src/App.jsx - Auth context → API server: auth requests
frontend/src/context/AuthContext.jsx - Booking pages → API client: calls
frontend/src/pages/ServiceRequests.jsx - Service workflows → API client: calls
frontend/src/pages/ServiceRequests.jsx - Finance pages → API client: calls
- Reporting page → API client: calls
- API client → API server: HTTP requests
- API server → Auth routes: mounts
backend/server.js - Auth routes → Authentication: dispatches
backend/routes/authRoutes.js - Auth routes → JWT access: verifies token
backend/routes/authRoutes.js - API server → Booking and rooms: routes requests
backend/server.js - API server → Guest management: routes requests
backend/server.js - API server → Service requests: routes requests
backend/server.js - API server → Payment processing: routes requests
backend/server.js - API server → Fees and tax rules: routes requests
backend/server.js - API server → Business reports: routes requests
backend/server.js - Authentication → MySQL database: queries
backend/controllers/authController.js - Booking and rooms → MySQL database: queries
backend/controllers/bookingController.js - Payment processing → MySQL database: queries
backend/controllers/paymentController.js - Fees and tax rules → MySQL database: queries
backend/controllers/taxDiscountController.js - Guest management → MySQL database: uses database
- Service requests → MySQL database: uses database
- Business reports → MySQL database: uses database