2017-08-02 21:05:10 +08:00
< p align = "center" >
< a href = "https://github.com/yiisoft" target = "_blank" >
< img src = "https://avatars0.githubusercontent.com/u/993323" height = "100px" >
< / a >
< h1 align = "center" > Yii 2 Basic Project Template< / h1 >
< br >
< / p >
2013-05-24 22:14:49 +08:00
2015-04-02 21:09:56 +08:00
Yii 2 Basic Project Template is a skeleton [Yii 2 ](http://www.yiiframework.com/ ) application best for
2014-02-16 00:57:11 +08:00
rapidly creating small projects.
2013-05-24 22:14:49 +08:00
2013-12-02 01:17:58 +08:00
The template contains the basic features including user login/logout and a contact page.
It includes all commonly used configurations that would allow you to focus on adding new
features to your application.
2013-05-24 22:14:49 +08:00
2018-02-19 04:48:18 +08:00
[![Latest Stable Version ](https://img.shields.io/packagist/v/yiisoft/yii2-app-basic.svg )](https://packagist.org/packages/yiisoft/yii2-app-basic)
[![Total Downloads ](https://img.shields.io/packagist/dt/yiisoft/yii2-app-basic.svg )](https://packagist.org/packages/yiisoft/yii2-app-basic)
2020-11-01 00:25:13 +08:00
[![build ](https://github.com/yiisoft/yii2-app-basic/workflows/build/badge.svg )](https://github.com/yiisoft/yii2-app-basic/actions?query=workflow%3Abuild)
2013-05-24 22:14:49 +08:00
DIRECTORY STRUCTURE
-------------------
2014-01-16 19:56:26 +08:00
assets/ contains assets definition
2013-05-24 22:14:49 +08:00
commands/ contains console commands (controllers)
config/ contains application configurations
controllers/ contains Web controller classes
2014-02-13 04:01:01 +08:00
mail/ contains view files for e-mails
2013-05-24 22:14:49 +08:00
models/ contains model classes
runtime/ contains files generated during runtime
2014-01-16 19:56:26 +08:00
tests/ contains various tests for the basic application
2013-05-24 22:14:49 +08:00
vendor/ contains dependent 3rd-party packages
views/ contains view files for the Web application
2013-07-25 19:57:49 +08:00
web/ contains the entry script and Web resources
2013-05-24 22:14:49 +08:00
REQUIREMENTS
------------
2019-12-24 18:09:46 +08:00
The minimum requirement by this project template that your Web server supports PHP 5.6.0.
2013-05-24 22:14:49 +08:00
INSTALLATION
------------
2016-09-07 17:46:48 +08:00
### Install via Composer
If you do not have [Composer ](http://getcomposer.org/ ), you may install it by following the instructions
at [getcomposer.org ](http://getcomposer.org/doc/00-intro.md#installation-nix ).
You can then install this project template using the following command:
~~~
2019-06-13 04:01:56 +08:00
composer create-project --prefer-dist yiisoft/yii2-app-basic basic
2016-09-07 17:46:48 +08:00
~~~
Now you should be able to access the application through the following URL, assuming `basic` is the directory
directly under the Web root.
~~~
http://localhost/basic/web/
~~~
2013-12-02 01:17:58 +08:00
### Install from an Archive File
2013-05-24 22:14:49 +08:00
2013-12-02 01:17:58 +08:00
Extract the archive file downloaded from [yiiframework.com ](http://www.yiiframework.com/download/ ) to
a directory named `basic` that is directly under the Web root.
2013-05-24 22:14:49 +08:00
2015-07-28 23:45:49 +08:00
Set cookie validation key in `config/web.php` file to some random secret string:
```php
'request' => [
// !!! insert a secret key in the following (if it is empty) - this is required by cookie validation
'cookieValidationKey' => '< secret random string goes here > ',
],
```
2013-12-02 01:17:58 +08:00
You can then access the application through the following URL:
2013-05-24 22:14:49 +08:00
~~~
2013-12-02 01:17:58 +08:00
http://localhost/basic/web/
2013-05-24 22:14:49 +08:00
~~~
2018-02-07 05:07:24 +08:00
### Install with Docker
Update your vendor packages
docker-compose run --rm php composer update --prefer-dist
Run the installation triggers (creating cookie validation code)
docker-compose run --rm php composer install
Start the container
docker-compose up -d
You can then access the application through the following URL:
http://127.0.0.1:8000
**NOTES:**
- Minimum required Docker engine version `17.04` for development (see [Performance tuning for volume mounts ](https://docs.docker.com/docker-for-mac/osxfs-caching/ ))
- The default configuration uses a host-volume in your home directory `.docker-composer` for composer caches
2014-01-16 19:56:26 +08:00
CONFIGURATION
-------------
### Database
Edit the file `config/db.php` with real data, for example:
```php
return [
2014-05-23 22:51:38 +08:00
'class' => 'yii\db\Connection',
'dsn' => 'mysql:host=localhost;dbname=yii2basic',
'username' => 'root',
'password' => '1234',
'charset' => 'utf8',
2014-01-16 19:56:26 +08:00
];
```
2015-10-21 09:07:07 +08:00
**NOTES:**
- Yii won't create the database for you, this has to be done manually before you can access it.
- Check and edit the other files in the `config/` directory to customize your application as required.
2015-11-29 15:03:37 +08:00
- Refer to the README in the `tests` directory for information specific to basic application tests.
2016-07-16 09:13:51 +08:00
TESTING
-------
2016-07-26 04:41:30 +08:00
Tests are located in `tests` directory. They are developed with [Codeception PHP Testing Framework ](http://codeception.com/ ).
By default there are 3 test suites:
- `unit`
- `functional`
- `acceptance`
Tests can be executed by running
```
2017-02-01 18:29:32 +08:00
vendor/bin/codecept run
2017-06-17 22:23:21 +08:00
```
2016-07-26 04:41:30 +08:00
The command above will execute unit and functional tests. Unit tests are testing the system components, while functional
tests are for testing user interaction. Acceptance tests are disabled by default as they require additional setup since
they perform testing in real browser.
2016-07-16 09:13:51 +08:00
2016-07-26 04:41:30 +08:00
### Running acceptance tests
2016-07-16 09:13:51 +08:00
To execute acceptance tests do the following:
1. Rename `tests/acceptance.suite.yml.example` to `tests/acceptance.suite.yml` to enable suite configuration
2016-07-26 04:41:30 +08:00
2. Replace `codeception/base` package in `composer.json` with `codeception/codeception` to install full featured
version of Codeception
2016-07-16 09:13:51 +08:00
3. Update dependencies with Composer
```
composer update
```
4. Download [Selenium Server ](http://www.seleniumhq.org/download/ ) and launch it:
```
2016-07-27 17:05:48 +08:00
java -jar ~/selenium-server-standalone-x.xx.x.jar
2017-02-03 06:03:05 +08:00
```
In case of using Selenium Server 3.0 with Firefox browser since v48 or Google Chrome since v53 you must download [GeckoDriver ](https://github.com/mozilla/geckodriver/releases ) or [ChromeDriver ](https://sites.google.com/a/chromium.org/chromedriver/downloads ) and launch Selenium with it:
```
# for Firefox
java -jar -Dwebdriver.gecko.driver=~/geckodriver ~/selenium-server-standalone-3.xx.x.jar
# for Google Chrome
java -jar -Dwebdriver.chrome.driver=~/chromedriver ~/selenium-server-standalone-3.xx.x.jar
2016-07-16 09:13:51 +08:00
```
2017-02-03 06:03:05 +08:00
As an alternative way you can use already configured Docker container with older versions of Selenium and Firefox:
```
docker run --net=host selenium/standalone-firefox:2.53.0
```
2016-07-16 09:13:51 +08:00
2020-09-09 06:38:53 +08:00
5. (Optional) Create `yii2basic_test` database and update it by applying migrations if you have them.
2016-07-16 09:13:51 +08:00
```
tests/bin/yii migrate
```
The database configuration can be found at `config/test_db.php` .
6. Start web server:
```
tests/bin/yii serve
```
7. Now you can run all available tests
```
# run all available tests
2017-02-01 18:29:32 +08:00
vendor/bin/codecept run
2016-07-16 09:13:51 +08:00
# run acceptance tests
2017-02-01 18:29:32 +08:00
vendor/bin/codecept run acceptance
2016-07-16 09:13:51 +08:00
# run only unit and functional tests
2017-02-01 18:29:32 +08:00
vendor/bin/codecept run unit,functional
2016-07-16 09:13:51 +08:00
```
2016-07-26 04:41:30 +08:00
### Code coverage support
2016-07-16 09:13:51 +08:00
By default, code coverage is disabled in `codeception.yml` configuration file, you should uncomment needed rows to be able
to collect code coverage. You can run your tests and collect coverage with the following command:
```
#collect coverage for all tests
2020-09-06 02:58:16 +08:00
vendor/bin/codecept run --coverage --coverage-html --coverage-xml
2016-07-16 09:13:51 +08:00
#collect coverage only for unit tests
2020-09-06 02:58:16 +08:00
vendor/bin/codecept run unit --coverage --coverage-html --coverage-xml
2016-07-16 09:13:51 +08:00
#collect coverage for unit and functional tests
2020-09-06 02:58:16 +08:00
vendor/bin/codecept run functional,unit --coverage --coverage-html --coverage-xml
2016-07-16 09:13:51 +08:00
```
2016-07-26 04:41:30 +08:00
You can see code coverage output under the `tests/_output` directory.