How huynhminhduc/tiemluc2019 works
Project type and purpose
• This is a monolithic, full-stack PHP web application built on the Yii2 framework.
• It provides a public frontend (search/browse data), an authentication & accounts module, plus several feature-specific modules (e.g., “iptc” for IP transfer, “quanly” for management, “sync” for data synchronization, “taisantritueadmin” for IP asset administration).
• It implements MVC and modular Yii2 patterns, with business logic in “services” classes, persistence in ActiveRecord models, presentation in view scripts, and controllers routing requests.
File-structure analysis
• Top-level application directories:
• config/ – application configs (web, console, DB, URL rules)
• assets/, modules/, widgets/ – reusable assets (CSS/JS), Yii modules, custom widgets
• commands/ – console commands (Yii console controllers)
• controllers/, models/, views/ – global MVC artifacts
• commons/, services/ – shared utilities and business-logic services
• codeception.yml + tests/ – acceptance/unit/functional tests
• web/ – public web root (index.php, assets deployment, uploads)
• docker-compose.yml, Vagrantfile, vagrant/ – local dev environment
• Each module folder uses the standard Yii2 layout (base controllers, controllers/, models/, views/, assets/, layouts/).
• config/* defines DB connections, parameters, route rules.
Key technical stack identified from README & files
• PHP 7.x, Yii2 framework (MVC + modules)
• MySQL (or PostgreSQL) via ActiveRecord
• Nginx + PHP-FPM (via Vagrant/Docker)
• Frontend assets: Dashmix, Bootstrap, jQuery, Slick, ApexCharts
• Console & codeception tests for CI.
Main architectural components
a. Client & presentation layer
• Browser (public & admin UIs)
• Assets (CSS/JS delivered from web/assets and modules/*/assets)
b. Web tier
• Nginx (or Apache) as reverse proxy/web server
• PHP-FPM process hosting Yii2 application
• Entry scripts: web/index.php (HTTP), console entry for CLI
c. Application layer (Yii2 monolith)
• Core: index.php → bootstrap → Yii application
• Modules:
– frontend (public search/browse)
– accounts (authentication & user management)
– auth (RBAC, roles, permission)
– iptc, quanly, sync, taisantritueadmin (feature areas)
• Controllers → Services → Models (ActiveRecord)
• Widgets as reusable UI components
• Shared commons/services for cross-module logic
d. Persistence & storage
• RDBMS (MySQL/PostgreSQL) for structured data
• File storage under web/uploads for file attachments
e. External & auxiliary
• Email (mail/* layouts)
• Third-party JS libs (ApexCharts, etc.)
• Vagrant/Docker for local dev/QA
• Codeception for testing
Interactions & data flow
• Browser → Nginx → web/index.php
• Yii2 router (URL rules) → appropriate module’s Controller
• Controller calls Service layer for business logic
• Service interacts with ActiveRecord models → DB
• Models may read/write file attachments → web/uploads
• Controller renders view with widgets & assets → Browser
• CLI console commands (commands/) interact with same Services/Models
Architectural patterns & design principles
• MVC (Model-View-Controller) core
• Modularization (Yii2 modules isolate feature domains)
• Service layer for business logic, separating it from controllers
• ActiveRecord for ORM
• Shared “commons” and “services” for cross-cutting concerns
• Widget abstraction for reusable UI components
Summary of essential elements to capture
• Clear separation: Presentation, Web server, Application modules, Services/Models, Data stores
• Module grouping: frontend, accounts/auth, iptc, quanly, sync, taisantritueadmin