How aaronmicarte/hellhotel works
HellHotel is a hotel reservation and billing system. Its main guest workflow is browsing rooms, selecting a room, submitting a reservation, and handling payment; staff use separate admin and front-desk screens to manage reservations, guests, rooms, billing, add-ons, and reports. The tree and sampled PHP show database-backed API operations, but README detail is limited and several endpoint implementations are unsampled, so those capabilities are represented without assuming undocumented call sequences.
Main entry points: database.php Hotel database · frontdesk Front-desk screens · admin Admin and front desk · rooms.js Room browsing
Components 22
Guest booking
- Guest pages
html/guest - Room browsing
assets/js/guest/rooms.js - Room selection
assets/js/guest/selected-room.js - Booking form
assets/js/guest/booking-form.js
Staff operations
- Admin and front desk
html/admin - Front-desk screens
html/frontdesk - Reservation management
assets/js/admin/reservations.js - Guest records
api/admin/guests/guests.php - Room management
assets/js/admin/rooms.js - Operational reports
api/admin/dashboard/frontdesk_reports.php - Staff accounts
api/admin/add-user/users.php
Billing and sales
- Billing operations
api/admin/billing/billing.php - Payment operations
api/admin/payments/payments.php - Add-on orders
api/admin/addons/order.php
API and persistence
- Reservations API
api/admin/reservations/reservations.php - Rooms API
api/admin/rooms/rooms.php - Session authentication
api/auth/login.php - Admin authorization
api/middleware/auth.php - Hotel database
api/config/database.php
Other components
- Guest
- Hotel staff
- Payment provider
Connections 28
- Guest → Guest pages: browses
- Guest pages → Room browsing: loads rooms
- Room browsing → Rooms API: requests availability
- Room browsing → Room selection: selects room
- Room selection → Booking form: continues booking
- Booking form → Reservations API: submits reservation
- Hotel staff → Admin and front desk: uses admin
- Hotel staff → Front-desk screens: uses front desk
- Admin and front desk → Session authentication: authenticates
- Front-desk screens → Session authentication: authenticates
- Reservation management → Reservations API: manages bookings
- Room management → Rooms API: manages rooms
- Admin and front desk → Guest records: manages guests
- Admin and front desk → Staff accounts: manages accounts
- Admin authorization → Hotel database: uses connection
- Reservations API → Hotel database: reads and writes
- Rooms API → Hotel database: reads and writes
- Guest records → Hotel database: reads and writes
- Staff accounts → Hotel database: reads and writes
- Billing operations → Hotel database: reads and writes
- Payment operations → Hotel database: reads and writes
- Add-on orders → Hotel database: reads and writes
- Operational reports → Hotel database: queries metrics
- Front-desk screens → Billing operations: handles billing
- Front-desk screens → Payment operations: records payments
- Front-desk screens → Add-on orders: manages orders
- Front-desk screens → Operational reports: views reports
- Payment provider → Payment operations: optional integration