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: "After installing Vagrant, we ran the vagrant command to check whether it was installed correctly."

A block of code is set as follows:

VAGRANTFILE_API_VERSION = "2"
Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
  config.vm.box = "base"
end

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

---
- hosts: default
  tasks:
  - name: update apt cache
    apt: update_cache=yes
  - name: ensure nginx is installed
    apt: pkg=nginx state=present
  - name: write the nginx config file
    template: src=nginx-default-site.conf dest=/etc/nginx/sites-available/default.conf
 notify:
 - restart nginx
  - name: ensure nginx is running
    service: name=nginx state=started
  handlers:
 - name: restart nginx
 service: name=nginx state=restarted

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

ansible-playbook our-playbook.yml -i our-inventory-file

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: "Again, on OS X, the first step is to double-click on the Vagrant.pkg icon."