Errata

"Instead of spending the first two days on the job installing software, a new development team member can spin up a production-identical environment on their laptop simply by typing vagrant init then vagrant up."

With "vagrant init", a new team usually does not get a production-identical environment since the command just sets up a default Vagrantfile without any provisioners enabled.

One could argue that you can pass a custom box to "vagrant init" and that the box would be some kind of golden image with everything required for a production-like setup. But considering that "vagrant provision" is mentioned shortly after, this doesn't seem to be what the author had in mind either:

"All the developers on the team can update their environments with a new software version in minutes, instead of hours, simply by typing vagrant provision."

When it comes to setting up production environments, it's most likely that you run "vagrant up" only. I suggest to remove the "vagrant init" here.

Note from the Author or Editor:
Change "simply by typing vagrant init then vagrant up" to just "simply by typing vagrant up"

The exclamation point in the sample command seems to confuse my Mac's bash shell, as it thinks the ! introduces a previous event specifier:

ratdog:vagrant_book_example mike$ echo "<strong>Hello!</strong>" >index.html
-bash: !: event not found

You can either use single quotes, or omit the !, or use a \ to avoid or escape the special meaning of the !

ratdog:vagrant_book_example mike$ echo '<strong>Hello!</strong>' >index.html
ratdog:vagrant_book_example mike$ echo "<strong>Hello\!</strong>" >index.html
ratdog:vagrant_book_example mike$

In Figure 3.1, the result of viewing the index doesn't have the ! in Hello! so it is inconsistent with the shell command.

Note from the Author or Editor:
Let's just remove the exclamation point in question. So that instead of "Hello!" it says "Hello"

web.vm.provision :shell, inline: "apt-get install mysql-client"

causes provisioning to fail due to it requiring explicit acknowledgement to install myself-client.

Adding " -y " after apt-get resolved the issue.

Note from the Author or Editor:
This is correct. The text "apt-get install mysql-client" needs to be changed to "apt-get -y install mysql-client"

This line:

web.vm.forwarded_port 80, 8080

Should be replaced by thus line:

web.vm.forward_port 80, 8080

(look at the syntax of the incorrect "forwarded_port" vs. the correct "forward_port")

Note from the Author or Editor:
Just as the detailed description says, "forwarded_port" should be "forward_port" in the code sample.

The connection to the "db" instance shouldn't be launched this way:

mysql -uroot -h192.168.33.10

but this way:

mysql -uroot -h192.168.33.11

(the correct IP of the "db" machine is 192.168.33.11, as configured in the previous Vagrantfle from page #71)

Note from the Author or Editor:
This is correct, as the detailed response says the line should be changed.

IP address of the database server is mistyped - it should be .11, not .10 as printed in the (epub) book, as we're contacting the db server:

ratdog:vagrant_book_example mike$ vagrant ssh web
Welcome to Ubuntu 12.04 LTS (GNU/Linux 3.2.0-23-generic x86_64)

* Documentation: https://help.ubuntu.com/
Welcome to your Vagrant-built virtual machine.
Last login: Fri Sep 14 06:23:18 2012 from 10.0.2.2
vagrant@precise64:~$ mysql -uroot -h192.168.33.10
ERROR 2003 (HY000): Can't connect to MySQL server on '192.168.33.10' (111)
vagrant@precise64:~$ mysql -uroot -h192.168.33.11
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 37
Server version: 5.5.31-0ubuntu0.12.04.2 (Ubuntu)

Copyright (c) 2000, 2013, Oracle and/or its affiliates. All rights reserved.

Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

mysql>

Note from the Author or Editor:
Correct. The code on page 102 should have "192.168.33.11" instead of "192.168.33.10" in the shell prompt where it is connecting to MySQL (the line that says "mysql -uroot"

It looks like we have dropped from using the instance variable @env to the non-existant local variable env in the code sample:

module MyVagrantPlugin
class Command < Vagrant.plugin("2", "command")
def execute
command = "grep MemFree /proc/meminfo | awk '{print $2}'"

with_target_vms(@argv) do |machine|
if machine.state.id != :running
env.ui.info("#{machine.name} is not running.")
next
end

machine.communicate.execute(command) do |type, data|
env.ui.info(data)
end
end

return 0
end
end
end

when I try "bundle exec vagrant free-memory" the stack trace begins with:

/Users/mike/Projects/my_vagrant_plugin/lib/my_vagrant_plugin/command.rb:13:in `block (2 levels) in execute': undefined local variable or method `env' for #<MyVagrantPlugin::Command:0x007f8bf22f38e0> (NameError)

Reverting to @env.ui.info seems to make everything happy again.

Note from the Author or Editor:
All instances of the word "env" in the code sample shown in this submission should be replaced with "@env"

I had to change the class name for the vagrant plugin configuration class I saved in lib/my_vagrant_plugin/provisioner_config.rb from Config to Plugin::ProvisionerConfig for the "bundle exec vagrant up" to work.

lib/my_vagrant_plugin/provisioner_config.rb on my system is:

module MyVagrantPlugin
class Plugin::ProvisionerConfig < Vagrant.plugin("2", "config")
attr_accessor :packages

def initialize
super
@packages = UNSET_VALUE
end

def finalize!
@packages = [] if @packages == UNSET_VALUE
end
end
end

Note from the Author or Editor:
On page 113 of the PDF, in the code sample shown in this screenshot: https://dl.dropbox.com/s/uusc8ip8l261vmq/s3.amazonaws.comormatlasprodbuilds1234000001668.pdfAWSAccessKeyIdAKIAI7JUEXOLC35F5P4QExpires1380689191SignatureX7cKKoOXA7K3mfI1tQzQoBb2BE83D_20131001_215503.png

The line that says "class Config" should be "class ProvisionerConfig"