The following is a proposed project structure for advanced applications that works in conjunction with YIInitializr components.
YIInitializr vanilla projects make extensive use of Composer. We found at 2amigos.us that is easier to your extensions bundle outside of your application scope - thanks to Phundament and Tobias Munk for his knowledge and shares. Composer is your dependency package best friend.
The package is cleaned from extensions, you choose what you wish to include in your composer.json files. The only ones included are Yii Framework (obviously), YiiStrap and YiiWheels, the rest is up to you. We do not want to confuse you.
api/config/
, frontend/config/
, console/config/
, backend/config/
and common/config/
to suit your needs. The common/config/main.php
is configured to use sqllite by default. Change your common/config/env/dev.php
to suit your database requirements.
composer.phar
file.composer.json
and remove the dependencies you don't need also update the required versions of the extensions.composer
installed globally:
composer self-update
to make sure you have the latest version of composer.composer install
to download all the dependencies.composer.phar
library within the project boilerplate.
php composer.phar self-update
to make sure you have the latest version of composer.php composer.phar install
to download all the dependencies.Yiinitializr\Composer\Callback
will configure everything required on your application: runtime
and assets
folders and migrations.When you first run install and after the deployment script installs the dependencies, creates your runtime and assets folders, it will ask you for your environment. Make sure you use "dev" for your local development settings and "stage" or "prod" for their respective environment types. Also, is important that the files are actually there, do not say "master" without "master.php" not being actually there.
For more information about using Composer please see its documentation.
This boilerplate is very similar to YiiBoilerplate but differs from it for the easiness of its configuration. We focused to release the pain of configuring your application and combine your configuration files. Yiinitializr\Helpers\Initializr
is very easy to use, check for example the bootstrap index.php
file at the frontend:
require('./../../common/lib/vendor/autoload.php');
require('./../../common/lib/vendor/yiisoft/yii/framework/yii.php');
Yii::setPathOfAlias('Yiinitializr', './../../common/lib/Yiinitializr');
use Yiinitializr\Helpers\Initializer;
Initializer::create('./../', 'frontend', array(
__DIR__ .'/../../common/config/main.php', // files to merge with
__DIR__ .'/../../common/config/env.php',
__DIR__ .'/../../common/config/local.php',
))->run();
For more information about Yiinitializr please check it at its github repo.
Bellow the directory structure used:
|-api
|---config
|-----env
|---controllers
|---extensions
|-----components
|-----filters
|---models
|---www
|-backend
|---components
|---config
|-----env
|---controllers
|---extensions
|---helpers
|---lib
|---models
|---modules
|---tests
|---views
|-----layouts
|-----site
|---widgets
|---www
|-----css
|-------fonts
|-----img
|-----js
|-------libs
|-common
|---components
|---config
|-----env
|---extensions
|-----components
|---helpers
|---lib
|-----YiiRestTools
|-------Common
|---------Enum
|---------Exception
|-------Helpers
|-----Yiinitializr
|-------Cli
|-------Composer
|-------Helpers
|-------config
|---messages
|---models
|---schema
|---widgets
|-console
|---commands
|---components
|---config
|-----env
|---data
|---extensions
|---migrations
|---models
|-frontend
|---components
|---config
|-----env
|---controllers
|---extensions
|---helpers
|---lib
|---models
|---modules
|---tests
|---views
|-----layouts
|-----site
|---widgets
|---www
|-----assets
|-----css
|-------fonts
|-----img
|-----js
|-------libs
The following extensions are part of YIInitializr-basic template:
web development has never been so fun
www.2amigos.us