How alvinrhd/cinemark_management works
Project type and purpose
• Full-stack, PHP web application for internal administrative management of Cinemark’s cinema chain.
• Key features: user authentication, CRUD on movies/salas/usuarios, report generation (PDF, charts), seating management, video asset presentation.
File structure
• Top-level:
– auth/ : login/logout workflows (login.php, procesos_login.php, logout.php)
– config.php : DB credentials, global settings
– db/ : schema script.sql
– functions/ : business-logic functions (cargar_asientos, editar, eliminar, gestionar)
– pages/ : “controller–view” scripts (index, peliculas, salass, usuarios, ventas, generar_pdf, grafico, analisis_datos)
– assets/ : static front-end (CSS, images, videos)
– uploads/ : runtime file storage (e.g. user-uploaded files)
– index.php : main router/landing page
• Pattern: Monolithic MVC-style PHP with folders separating auth, business logic, views, and assets.
Extract insights from README
• Confirms internal admin system.
• No microservices or external APIs mentioned beyond typical PHP libraries (PDF generation, chart libraries).
Main components & interactions
a. Browser / Client (Admin UI)
– Loads HTML/CSS/JS from assets/ and pages/*.php
– Sends HTTP(S) requests (login, CRUD, report generation).
b. Web Server & PHP Application
– Apache/Nginx + PHP engine
– Routes requests via index.php or direct to pages/*.php and auth/*.php
– Calls functions in functions/*.php
– Reads config.php for DB connection
c. Database (MySQL/MariaDB)
– Defined by db/script.sql
– Stores users, movies, salas, ventas, seating, etc.
d. File Storage
– assets/ for static files
– uploads/ for dynamic user files (e.g., images, CSV imports)
e. Report/Chart Service (internal PHP libraries)
– pages/generar_pdf.php → PDF generator (e.g., TCPDF)
– pages/grafico.php → chart library (e.g., Chart.js)
f. External Dependencies (implicit)
– CSS/JS frameworks loaded locally under assets/css
– No third-party APIs or microservices evident.
Architectural patterns & principles
• Clear separation:
– Presentation (pages/, assets/)
– Business logic (functions/)
– Persistence (config.php → MySQL)
• Stateless HTTP requests with sessions for auth
• Modular PHP includes (require config.php + functions/*.php in pages)
• CRUD-oriented controllers in pages + processes in functions/