user avatar
Merge pull request #4387 from BackSlasher/allow-sudo
Mitchell Hashimoto authored
Ignoring SSHKeyBadOwner if user is root (uid 0)
417c2b7c
Name Last commit Last update
bin core: clean up Bundler tempfiles [GH-4103]
contrib Merging in latest version from kura/vagrant-bash-completion
keys Fix doc link [GH-3978]
lib Merge pull request #4387 from BackSlasher/allow-sudo
plugins guests/linux: backoff a bit on the mount timeout [GH-4403]
scripts scripts: calculate shasum
tasks update rake tasks for acceptance testing
templates guests/linux: more verbose output when shared folder mount fails
test Use -f argument to rm to force-remove files.
website typofixes - https://github.com/vlajos/misspell_fixer
.gitignore Vagrantfile for vagrant dev [GH-4089]
.travis.yml Speed up nokogiri installation during Travis runs
.vimrc .vimrc with vagrant tabstop settings
.yardopts YARD and some documentation
CHANGELOG.md communicators/ssh: cleanup PTY code for GH-4408]
CONTRIBUTING.md Add notes about debugging logs to contributing guidelines
Gemfile Update dep of ChildProcess to 0.4.0
LICENSE 🎆 New year! 🎆
README.md Update README
Rakefile Change symbols inside hashes to 1.9 JSON-like syntax
Vagrantfile Vagrantfile for vagrant dev [GH-4089]
vagrant-spec.config.example.rb core: Within a Bundler env, don't manage Bundler
vagrant.gemspec Update net-ssh dep [GH-3605]
version.txt Up version for dev

Vagrant

Vagrant is a tool for building and distributing development environments.

Development environments managed by Vagrant can run on local virtualized platforms such as VirtualBox or VMware, in the cloud via AWS or OpenStack, or in containers such as with Docker or raw LXC.

Vagrant provides the framework and configuration format to create and manage complete portable development environments. These development environments can live on your computer or in the cloud, and are portable between Windows, Mac OS X, and Linux.

Quick Start

For the quick-start, we'll bring up a development machine on VirtualBox because it is free and works on all major platforms. Vagrant can, however, work with almost any system such as OpenStack, VMware, Docker, etc.

First, make sure your development machine has VirtualBox installed. After this, download and install the appropriate Vagrant package for your OS.

To build your first virtual environment:

vagrant init hashicorp/precise32
vagrant up

Note: The above vagrant up command will also trigger Vagrant to download the precise32 box via the specified URL. Vagrant only does this if it detects that the box doesn't already exist on your system.

Getting Started Guide

To learn how to build a fully functional development environment, follow the getting started guide.

Installing the Gem from Git

If you want the bleeding edge version of Vagrant, we try to keep master pretty stable and you're welcome to give it a shot. The following is an example showing how to do this:

rake install

Ruby 2.0 is needed.

Contributing to Vagrant

Dependencies and Unit Tests

To hack on vagrant, you'll need bundler which can be installed with a simple gem install bundler. Afterwards, do the following:

bundle install
rake

This will run the unit test suite, which should come back all green! Then you're good to go!

If you want to run Vagrant without having to install the gem, you may use bundle exec, like so:

bundle exec vagrant help

NOTE: By default running Vagrant in via bundle will disable plugins. This is necessary because Vagrant creates its own private Bundler context (it does not respect your Gemfile), because it uses Bundler to manage plugin dependencies.

Acceptance Tests

Vagrant also comes with an acceptance test suite that does black-box tests of various Vagrant components. Note that these tests are extremely slow because actual VMs are spun up and down. The full test suite can take hours. Instead, try to run focused component tests.

To run the acceptance test suite, first copy vagrant-spec.config.example.rb to vagrant-spec.config.rb and modify it to valid values. The places you should fill in are clearly marked.

Next, see the components that can be tested:

$ rake acceptance:components
cli
provider/virtualbox/basic
...

Then, run one of those components:

$ rake acceptance:run COMPONENTS="cli"
...