Conventions

In this book, you will find a number of text styles that distinguish between different kinds of information. Here are some examples of these styles and an explanation of their meaning.

Code words in text, database table names, folder names, filenames, file extensions, pathnames, dummy URLs, user input, and Twitter handles are shown as follows: " This script tells Composer that when the create-project command is run, it should run the postCreateProject static function."

A block of code is set as follows:

"scripts": {
    "post-create-project-cmd": [
        "yii\\composer\\Installer::postCreateProject"
    ]
}

When we wish to draw your attention to a particular part of a code block, the relevant lines or items are set in bold:

// Define our application_env variable as provided by nginx/apache
if (!defined('APPLICATION_ENV'))
{
    if (getenv('APPLICATION_ENV') != false)
        define('APPLICATION_ENV', getenv('APPLICATION_ENV'));
    else 
       define('APPLICATION_ENV', 'prod');
}

$env = require(__DIR__ . '/config/env.php');

Any command-line input or output is written as follows:

$ ./yii fixture/load <FixtureName>
$ ./yii fixture/unload <FixtureName>

New terms and important words are shown in bold. Words that you see on the screen, for example, in menus or dialog boxes, appear in the text like this: " Once we have specified all the necessary attributes, we can click on the Preview button to preview our form, and then we can click on the Generate button to generate the source code."

Note

Warnings or important notes appear in a box like this.

Tip

Tips and tricks appear like this.