haskal
/
vagrant
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
4,999 Commits 8 Branches 143 Tags 51 MiB
Ruby 93.7%
HTML 3.3%
PowerShell 1.4%
Shell 0.8%
CSS 0.7%
Go to file
Mitchell Hashimoto 0f2fff2420 Merge pull request #2943 from mitchellh/f-boxes-2 
Boxes Revamp: Short URLs, Versions, Updates!

* **Box versioning** - All boxes can have versions now. This version information is available in metadata requested by Vagrant. New commands such as `vagrant box outdated` and new settings such as `config.vm.box_check_update` will configure how/when Vagrant checks for box updates. Boxes that don't support versions will always have version "0".

* **Shortnames for boxes** - You can now do things like `vagrant box add hashicorp/precise64`. The name and the URL are one and the same. This requires a backend. We'll be hosting one [for free public access] in the coming month or two. Of course, you don't need to use the backend we'll provide to support versions or unversioned boxes. You would need to for shortnames.

* **Multiple providers at one URL** - A single URL can now represent multiple providers. In this case, Vagrant will ask you what provider you want to download if it can't figure it out on its own. 

All of this is _fully backwards compatible_. I verified this as best I could with the tests in vagrant-spec. I have  to write new acceptance tests for the new features, however. Also, this PR adds around 100 unit tests.
 		2014-02-06 20:09:56 -08:00
bin core: Only load default and plugin Bundler groups to avoid dev deps 2014-01-31 16:42:53 +01:00
contrib Improved autocompletion for bash 2013-05-24 13:45:44 +04:00
keys Remove reference to PPK in keys readme 2013-07-18 10:52:38 -04:00
lib core: Add the default server URL 2014-02-05 21:20:37 -08:00
plugins kernel/v2: check for box updates by default 2014-02-05 21:20:33 -08:00
scripts scripts: calculate shasum 2013-12-09 00:17:14 -08:00
tasks update rake tasks for acceptance testing 2013-12-05 14:24:10 -08:00
templates core: shorthand boxes must be foo/bar formatted, better errors 2014-02-05 21:20:31 -08:00
test Fix tests for kernel/v2 2014-02-05 21:24:34 -08:00
website website/docs: update all the links to the box directory 2014-02-05 21:20:36 -08:00
.gitignore website/docs: document Vagrantfile updates 2014-02-05 21:20:26 -08:00
.travis.yml Install Bundler 1.5.2 for tests 2014-01-16 09:36:26 -08:00
.vimrc .vimrc with vagrant tabstop settings 2013-10-22 08:24:58 +02:00
.yardopts YARD and some documentation 2010-09-22 09:43:30 -06:00
CHANGELOG.md guests/linux: don't chown VB shared folders if readonly [GH-2442] 2014-02-04 16:01:14 +01:00
CONTRIBUTING.md Add notes about debugging logs to contributing guidelines 2013-06-09 20:42:31 -03:00
Gemfile Update dep of ChildProcess to 0.4.0 2014-01-17 20:34:58 -08:00
LICENSE 🎆 New year! 🎆 2014-01-02 00:48:22 -02:00
README.md Update README 2014-01-07 14:22:59 -08:00
Rakefile stdout.sync = true for rake tasks. 2011-11-13 19:41:38 -08:00
vagrant-spec.config.example.rb core: Within a Bundler env, don't manage Bundler 2014-01-17 09:39:20 -08:00
vagrant.gemspec Update dep of ChildProcess to 0.4.0 2014-01-17 20:34:58 -08:00
version.txt Make version 1.5.0.dev for semver 2014-02-02 16:52:41 +01:00

README.md

Vagrant

Vagrant is a tool for building and distributing development environments.

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

First, make sure your development machine has VirtualBox installed. After this, download and install the appropriate Vagrant package for your OS. If you're not on Mac OS X or Windows, you'll need to add /opt/vagrant/bin to your PATH. After this, you're ready to go!

To build your first virtual environment:

vagrant init precise32 http://files.vagrantup.com/precise32.box
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 rails development environment, view 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. Afterwords, 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"
...