» Vagrantfile

Vagrant is meant to run with one Vagrantfile per project, and the Vagrantfileis supposed to be committed to version control. This allows other developersinvolved in the project to check out the code, run vagrant up, and be ontheir way. Vagrantfiles are portable across every platform Vagrant supports.

The syntax of Vagrantfiles is , but knowledgeof the Ruby programming language is not necessary to make modifications to theVagrantfile, since it is mostly simple variable assignment. In fact, Ruby is noteven the most popular community Vagrant is used within, which should help showyou that despite not having Ruby knowledge, people are very successful withVagrant.

This feature lets you run vagrant from any directory in your project.

You can change the starting directory where Vagrant looks for a Vagrantfileby setting the environmental variable to some other path.

An important concept to understand is how Vagrant loads Vagrantfiles. Vagrantactually loads a series of Vagrantfiles, merging the settings as it goes. Thisallows Vagrantfiles of varying level of specificity to override prior settings.Vagrantfiles are loaded in the order shown below. Note that if a Vagrantfileis not found at any step, Vagrant continues with the next step.

• Vagrantfile packaged with the box that is to be usedfor a given machine.
• Vagrantfile in your Vagrant home directory (defaults to ~/.vagrant.d).This lets you specify some defaults for your system user.
• if any.
• Provider-specific overrides,if any.At each level, settings set will be merged with previous values. What thisexactly means depends on the setting. For most settings, this means thatthe newer setting overrides the older one. However, for things such as definingnetworks, the networks are actually appended to each other. By default, youshould assume that settings will override each other. If the behavior isdifferent, it will be noted in the relevant documentation section.

Within each Vagrantfile, you may specify multiple Vagrant.configure blocks.All configurations will be merged within a single Vagrantfile in the orderthey're defined.