Yii 2 Practical A Application Template
Yii 2 Practical-A Project Template is a skeleton Yii 2 application based on the yii2-advanced template best for developing complex Web applications with multiple tiers. The template allows a practical method to directly access the frontend from the app root and a simplified way to access backend.
The template includes three tiers: front end, back end, and console, each of which is a separate Yii application.
The template is designed to work in a team development environment. It supports deploying the application in different environments.
After installing an
app in the yii2-advanced application you normally would access the
frontend and backend by:
However, in many practical scenarios (especially on shared and single domain hosts) one would want their users to directly access frontend and backend as:
yii2-app-practical-a enables you to achieve just that by carefully moving and rearranging the
bootstrap files and web components of frontend to work directly out of the app root and backend out
backend/web folders are entirely eliminated and one can
directly access the application frontend this way:
and backend this way
All other aspects of the app configuration remain the same as the yii2-advanced app. The
will remain as is. The frontend config, assets, models, controllers, views, widgets and components, will still reside within
frontend directory. The backend config, assets, models, controllers, views, widgets and components, will still reside within
backend directory. It is just the web access that is moved out to app root for frontend and to the backend root folder for
- The template has some security preconfigured for users with Apache web servers. It has a default
.htaccesssecurity configuration setup.
- The template has prettyUrl enabled by default and the changes have been made to
.htaccessas well as
urlManagercomponent config in the common config directory.
- The template has isolated cookie settings for backend and frontend so that you can seamlessly access frontend and backend from same client.
The config files includes special
csrfcookie parameter settings for backend. Edit it according to your needs if necessary.
Detailed documentation can be referred at docs/guide/README.md.