99 lines
4.0 KiB
Markdown
99 lines
4.0 KiB
Markdown
# Vagrant
|
|
|
|
* Website: [https://www.vagrantup.com/](https://www.vagrantup.com/)
|
|
* Source: [https://github.com/hashicorp/vagrant](https://github.com/hashicorp/vagrant)
|
|
* [](https://gitter.im/mitchellh/vagrant)
|
|
* Mailing list: [Google Groups](https://groups.google.com/group/vagrant-up)
|
|
* IRC: #vagrant on freenode.org
|
|
|
|
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
|
|
|
|
Package dependencies: Vagrant requires `bsdtar` to be available on your system PATH to run successfully.
|
|
|
|
For the quick-start, we'll bring up a development machine on
|
|
[VirtualBox](https://www.virtualbox.org/) because it is free and works
|
|
on all major platforms. Vagrant can, however, work with almost any
|
|
system such as [OpenStack](https://www.openstack.org/), [VMware](https://www.vmware.com/), [Docker](https://docs.docker.com/), etc.
|
|
|
|
First, make sure your development machine has
|
|
[VirtualBox](https://www.virtualbox.org/)
|
|
installed. After this,
|
|
[download and install the appropriate Vagrant package for your OS](https://www.vagrantup.com/downloads.html).
|
|
|
|
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](https://www.vagrantup.com/docs/getting-started/index.html).
|
|
|
|
## Installing from Source
|
|
|
|
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. Please review the installation page [here](https://www.vagrantup.com/docs/installation/source.html).
|
|
|
|
## Contributing to Vagrant
|
|
|
|
Once your Vagrant bundle is installed from Git repository, you can run the test suite with:
|
|
|
|
bundle exec rake
|
|
|
|
This will run the unit test suite, which should come back all green!
|
|
|
|
If you are developing Vagrant on a machine that already has a Vagrant package installation present, both will attempt to use the same folder for their configuration (location of this folder depends on system). This can cause errors when Vagrant attempts to load plugins. In this case, override the `VAGRANT_HOME` environment variable for your development version of Vagrant before running any commands, to be some new folder within the project or elsewhere on your machine. For example, in Bash:
|
|
|
|
export VAGRANT_HOME=~/.vagrant-dev
|
|
|
|
You can now run Vagrant commands against the development version:
|
|
|
|
bundle exec vagrant
|
|
|
|
Please take time to read the [HashiCorp Community Guidelines](https://www.hashicorp.com/community-guidelines) and the [Vagrant Contributing Guide](https://github.com/hashicorp/vagrant/blob/master/.github/CONTRIBUTING.md).
|
|
|
|
Then you're good to go!
|
|
|
|
### 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"
|
|
...
|
|
```
|