This Vagrant file specifies two different VMs. At Zimco we have a Google Doc spreadsheet that keeps track of all our Vagrantfile VMs so we don’t need to worry about conflicts (that way we can have multiple projects running at the same time in case we need to jump over and fix a quick bug or eight).įor our example our initial (see below for the final) Vagrantfile looks like this: nfigure('2') do |config| You absolutely need to make sure you give them a unique hostname, IP address, and name setting so there aren’t conflicts. Vagrant allows us to define more virtual machines by wrapping them in blocks like the following: config.vm.define ' ' do || => default: Destroying VM and associated drives. If we don’t destroy this box before we do the next step we’ll leave it running and taking up disk space so we’re going to destroy it: $ vagrant destroyĭefault: Are you sure you want to destroy the 'default' VM? y

If you’ve worked with Vagrant before you’ve seen this a MILLION times but I want to draw your attention to the “default” text that shows up over and over again. default: /vagrant => /Users/scottkeckwarren/blah => default: Importing base box 'precise64'. Then to make sure everything is working correctly: $ vagrant upīringing machine 'default' up with 'virtualbox' provider. I’m going to use the basic configuration we created in Getting Started With Vagrant stripped down to the very basics: nfigure('2') do |config|Ĭonfig.vm.network :private_network, ip: '192.168.56.101' Because of this we need to work with multiple VMs in the same Vagrant file which isn’t covered by most tutorials. We’re starting to work on scaling STAGES from a single server to multiple servers so I’m using Vagrant as the test bed for this process. One of the things I love about Vagrant is how it allows you to quickly create a VM that is very close to your production environment (or better yet EXACTLY like it).

Vagrant virtualbox provider