How script-php/easyapp works
Project type and purpose
• EasyAPP is a PHP-based, monolithic MVC framework plus application scaffold.
• Purpose: provide a lightweight, easy-to-maintain structure for any PHP website.
File structure
• Top level “index.php” and “.htaccess”: front-controller pattern, all HTTP requests funnel here.
• “system/”: core framework code (Autoloader, Controller base classes, Framework modules for Config, Db, Request, Response, Event, etc.).
• “app/”: application-specific MVC layers:
• app/config.php – global settings
• app/controller – HTTP action handlers
• app/model – business-logic/data models
• app/view – HTML templates
• app/language – i18n strings
• app/helper.php – utility functions
• “assets/”: public static files (JS, CSS, images).
• “storage/”: runtime data (cache, logs, sessions, uploads).
• “composer.json/lock”: external libraries.
• “tests/”: automated unit and integration tests structure.
Key insights from README
• Clean, maintainable code with no spaghetti.
• Lightweight footprint, PHP 7.0+ requirement.
Main components
a. External clients & transport
• Browser or HTTP client → Web server (Apache/Nginx)
• .htaccess rewrite to /index.php
b. PHP runtime & autoloader
• Autoloader (system/Autoloader.php)
c. Framework core (system/Framework components)
• Request → Router → Controller dispatcher
• Config loader
• Db layer (system/Framework/Db.php)
• Event bus (system/Framework/Event.php)
• Language loader
• Loader (view/template engine)
• Response builder
d. Application layer (app/)
• Controllers
• Models
• Views (templates)
• Helpers & language files
e. Data stores & storage
• Relational database (MySQL, PostgreSQL, etc.) via Db abstraction
• Local filesystem (storage/cache, logs, sessions, uploads)
f. External dependencies
• Composer-installed libraries (system/Vendor + vendor/)
• Mail service (system/Framework/Mail.php)
• Image processor (system/Framework/Image.php)
Relationships & data flow
1. Client issues HTTP request → Web server
2. .htaccess routes to index.php → Autoloader loads core classes
3. Framework bootstraps: Config, Registry, Event system
4. Request parsed → Router chooses Controller & Action
5. Controller invokes Models (Db queries) and Helpers
6. Data enriched via Events or Language loader
7. Controller passes data to View → Template rendered
8. Response sent back to client
9. During steps, storage is used for sessions, cache, logs, uploads
Architectural patterns & principles
• Front Controller (all requests through index.php)
• MVC separation (Controllers, Models, Views)
• Dependency Registry / Service Locator
• Event-driven hooks
• Autoloading & PSR-like structure
• Layered file storage for cache/logs/sessions
Detail level
• Call out the front-controller (.htaccess → index.php → Autoloader).
• Test harness separately if desired (tests/ folder invoking Controllers & Models).