How bryanmg20/hotel_laureles works
Project type and purpose
• This is a full-stack hotel reservation web application (“Hotel_Laureles”).
• Frontend: React (SPA) served via Nginx in Docker.
• Backend: Python Flask REST API in Docker, implements reservation, check-in/out, billing, payments, room management, user management.
• Persistence: MySQL database in Docker, initialized via los_laureles.sql.
File structure
• Top-level directories:
• backend/ – Flask service
• fronted/ – React client (typo “fronted” rather than “frontend”)
• mysql/ – MySQL service and init script
• backend/app/models → ORM models (Habitacion, Usuario)
• backend/app/routes → REST endpoints (admin_* and user routes)
• fronted/src/components → UI components (public & admin)
• fronted/src/context → React Contexts (AuthContext, CartContext)
• Docker-related files in each service: Dockerfile(.dev), docker-compose.yml, .env
README
• Minimal description: “Proyecto final de base de datos.”
Components
a. Main Components
1. Client Browser (User & Admin UIs)
2. Nginx Reverse Proxy / Static Server (serves React build)
3. React Application (SPA)
4. Flask REST API
5. MySQL Database
6. Docker Compose Network (orchestrates containers)
b. Relationships & Data Flows
• Browser ↔ (HTTPS) ↔ Nginx ↔ React App
• React App → (REST calls) → Flask API
• Flask API ↔ (SQL queries) ↔ MySQL DB
• Admin UI (subset of React) ↔ same Flask API endpoints
c. Architectural Patterns / Principles
• Container-based microservices (three containers)
• Stateless RESTful API
• React Context for state (Auth, Cart)
• Separation of concerns: presentation (React), business logic (Flask), persistence (MySQL)
d. Key Technologies
• Docker & Docker Compose
• Nginx
• React (JSX, Context API)
• Flask (Python, blueprinted routes)
• MySQL