Vagrant: Up and Running: Create and Manage Virtualized Development Environments

Published in 2013, a lot of the syntax and keywords have since changed. The worst thing about Vagrant is its documentation and this book does more harm than good by giving you incorrect information. It needs an update. Do yourself a favor and skip this.

This book was written for Vagrant 1.x. Although the book itself promises that the information will also be applicable to Vagrant 2.x (which was not yet released at the time it was written), in reality the most basic examples in the first couple chapters are already failing due to things that have changed since the book was published. For example, the first “vagrant init” command they have you do references a box URL that isn’t reachable anymore (and so the subsequent “vagrant up” fails to download it), and the instructions on how to set up a shared filesystem use a configuration attribute that no longer exists in Vagrant 2. The book is still useful as a conceptual introduction to Vagrant, but it is not suitable as a step by step guide, unfortunately.

We have been using Vagrant for about six months now. I have put off too long diving into the subject. The fact that I could put it off is a demonstration of one of Vagrant's strengths: a team can use it without having a lot of knowledge about how it works. It just works. But as an engineer, I wanted to know more about how our Vagrant environments were configured, especially since we're now using Docker inside Vagrant, and I was not entirely clear on the boundaries between my host machine, Vagrant, a VirtualBox, and Docker containers.In about 4 hours, I was able to work through the first six of seven chapters of the book, including time to experiment with creating and destroying Vagrant environments. The last little exercise was creating a two-node cluster, one of which installed and ran MySQL, the other installed and ran Apache. And then confirming that networking was running properly between them, and the host. Along the way, I won't say I gained a complete education on the ins and outs of Vagrant, but I learned much, and now feel confident that I can go to Vagrant's online documentation and find any further information I need. This book did a great job of explaining the why as well as the how of Vagrant.Considering I got this as a Kindle book for about half the print price, it was really a great bargain. If you're looking to bootstrap your knowledge of Vagrant, I recommend this book.(One little sidenote: If you try the hostonly example, and the 192.168.33.* subnet doesn't work for you, try 192.168.133.*.)

When you go to the author's site, and you click on the link, on the author's site, you might anticipate the text would be totally accurate and up-to-date.It is a good overview -- more complete than the web site, but some of the examples and commands are out-dated. I am having to go through both the web site and the book, making notes about the "correct" commands. This was not a complete waste of money, but it certainly was not the "valuable resource" I was hoping for.I contribute to the open source projects I use and like. I guess this was my contribution to Vagrant.Don't get me wrong about Vagrant. I still am quite happy with what it is doing for me! I just wish the book was up-to-date.

A week ago I knew nothing about Vagrant. I looked for a book on Vagrant, finding this one. The reviews were mostly positive. Amazon let me use the book on trial basis for my tablet Kindle application. What did I have to lose? Within a few hours I felt comfortable with Vagrant, especially in conjunction with provisioning. I used the book several times as a provisioning reference-by-example. A slight disappointment is that I'd like so see an edition with a Docker provisioning chapter. In the end, I now will actually buy the book so I can see it on my development machine with unlimited availability. It was smart of Amazon, or the publisher, to make this book available on a trial basis. I perhaps may not have purchased it otherwise.

Well written, clear and concise - however is from 2013 - which in the computer world is crazy out of date. The first think I looked up was a configuration option - the book had v1 options, which are different from the v2 options. Specifically, it has config.vm.host_name which has now been updated to config.vs.hostname - not a big difference, but the first one gives an error at vagrant up and the second one works.

This is a perfect primer and I wish I had sprung the cash to buy this instead of trying to fumble through the online documentation. The only issue I have with this book is that it's not up to date. With version two of the Vagrant API you'll have to adjust many of the commands in the book to the new version which kind of makes the examples moot. All that aside the theoretical and philosophical basis for this vm provisioner is very clearly explained in this book. Definitely worth buying on Kindle, but I hope they update the content soon.

I very much enjoyed this book - was a great help at getting Vagrant set up.Here's the problem I have with it - it's very similar to the Vagrant "Getting Started" tutorial on their website (http://docs.vagrantup.com), written by the same person. If you don't mind paying for information that you can realistically get on the Internet (I was fine with it), then this is a good book. Hard to fault Vagrant for having documentation that's *too* good, honestly. :)

I must confess I arrived to the vagrant party pretty late. But, the cool thing about vagrant, is you can get up and running really quickly, making it an ideal tool in the delivery process for the seasoned and uninitiated alike.After using vagrant for a while, I wanted to do more with it, but didn't have the time to figure it out. So when Mitchell Hashimoto released Vagrant Up, I was curious. I grabbed the kindle copy, and I am glad to say, I wasn't disappointed. Chapter 7 where he delves into plugin development was the real seller for me. Within a couple of hours, I had written a plugin and got me thinking about other possibilities. Even though a reasonable knowledge of ruby is required, the author goes over the internals with an easy-going style. I definitely recommend this book to anyone involved with DevOps, automation or the software delivery process.

It was out-of-date in 2015, six years later it's worthless.

Covers the basic subject matter well. It is a little out of date in some areas and the coverage of Windows is virtually non-existent. But not bad as an introductory guide. Could do with an update to a more recent version and include mentions of other providers such as AWS which is clearly increasingly popular.

Unfortunately not very detailed. This book only explains the very basics, which any Vagrant user will already know. This doesn't go into topics like using Jenkins to spin up a cluster of Vagrant instances and run parallel tests across them. That's obviously a specific use case, so expecting that exact topic is a stretch, but you'd expect at least 2-3 complex use cases, not just "run vagrant up to have a VM!".

Rather out of date. Doesn't cover much more than Vagrant's website.