How mehmettilhann/arabalazim works
Project Type & Purpose
• Full-stack, server-rendered PHP web application for vehicle rental and sales.
• Two user roles: End users (browse/list/rent/buy cars, comment, account management) and Admins (CRUD on cars, users, comments, view transactions, configure settings).
Core Components
a. Clients
• Web browser (desktop/mobile) – sends HTTP(S) requests and renders HTML/CSS/JS.
b. Web/Application Server
• Apache/Nginx + PHP-FPM executing PHP scripts.
• Entry-points:
– Root scripts (Arabalazim.php, contact_us.php, etc.)
– Module folders:
• login-register/ (authentication, password reset)
• arac-kirala/ (car catalog, details, booking, comments)
• admin/ (admin dashboard and management pages)
– Composer-managed PHPMailer library for outbound email.
c. Data Store
• MySQL database (users, cars, bookings, comments, transactions).
d. External Services
• SMTP server (via PHPMailer) for email notifications (password reset, booking confirmations).
e. Static Assets
• CSS, JS, images served from the same web server.
Relationships & Data Flows
• User Browser →(HTTPS)→ Web Server: page requests, form submissions.
• Web Server → PHP Modules: authentication, business logic.
• PHP Modules → MySQL: SELECT/INSERT/UPDATE queries.
• PHP Modules → PHPMailer → SMTP: send email.
• Web Server → Browser: HTML/CSS/JS responses.
• Admin Panel ↔ Database: manage cars, users, comments, orders.
Architectural Patterns & Principles
• Monolithic-modular structure: folder per feature (login, rental, admin).
• Separation of concerns:
• Presentation (HTML, CSS, JS)
• Application logic (PHP scripts)
• Data persistence (MySQL)
• Externalize email logic via PHPMailer library (composer dependency).