How uzairayed/maju-parking-system works
Project Type and Purpose
• This is a monolithic full-stack PHP/MySQL web application (no separate “frontend” and “backend” repos).
• Users interact via web pages (e.g., index.php, admin.php) to perform CRUD operations on questions.
File Structure
• Top-level scripts (controllers):
• index.php – landing page/login/form
• admin.php – question admin dashboard
• .php – list or view questions
• updateQue(B).php & updateQue(C).php – editing questions (two variants)
• delete.php – question deletion
• Static assets: queStyle.css, style.css
• Deployment bundle: MPS.zip, intended for XAMPP’s htdocs.
• Database interaction lives inside each PHP script using MySQL calls.
Extract Additional Insights from README
• Requires XAMPP (Apache + PHP + MySQL).
• Deploy by unzipping into htdocs/ and accessing via localhost.
Main Components & Their Relationships
a. Client Browser
– Requests PHP pages, loads CSS; submits forms.
b. Web Server & PHP Runtime (Apache + mod_php under XAMPP)
– Receives HTTP requests, invokes the appropriate .php script.
c. Application Logic Modules (the .php files)
– index.php handles authentication/landing.
– admin.php loads admin operations view.
– display.php reads and renders questions.
– updateQue(B/C).php process updates.
– delete.php handles removals.
d. MySQL Database
– Stores question data, user credentials, etc.
– Each PHP module issues SQL queries (SELECT, INSERT, UPDATE, DELETE).
e. Static File Server
– Serves CSS files (queStyle.css, style.css).
Architectural Patterns & Design Principles
• Monolithic structure: all code lives in one tier.
• Implicit MVC:
– Controllers = your .php scripts
– Views = embedded HTML/CSS in those scripts
– Model = MySQL tables accessed directly
• Separation of concerns is minimal; each PHP script handles both view and DB logic.