Conventions

In this book, you will find a number of styles of text 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: "Make sure the log-runtime-metrics plugin is installed and the application was restarted."

A block of code is set as follows:

worker_processes Integer(ENV['WEB_CONCURRENCY'] || 2)
timeout Integer(ENV['WEB_TIMEOUT'] || 15)
listen ENV['PORT'], backlog: Integer(ENV['UNICORN_BACKLOG'] || 50)
preload_app true

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

worker_processes Integer(ENV['WEB_CONCURRENCY'] || 2)
timeout Integer(ENV['WEB_TIMEOUT'] || 15)
listen ENV['PORT'], backlog: Integer(ENV['UNICORN_BACKLOG'] || 50)
preload_app true

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

# cp /usr/src/asterisk-addons/configs/cdr_mysql.conf.sample
 /etc/asterisk/cdr_mysql.conf

New terms and important words are shown in bold. Words that you see on the screen, in menus or dialog boxes for example, appear in the text like this: "We will need to fill in our applications URL and then click on Load test execution plan."

Note

Warnings or important notes appear in a box like this.

Tip

Tips and tricks appear like this.