haskal
/
vagrant
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
616 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 f30cdf3eea New wrapper SSH session class to emit exit status as well. Will be used in the future to raise exceptions for bad exit status. For now, works as a drop-in replacement. 2010-05-28 14:19:35 -07:00
bin Update binary to not include rubygems 2010-04-13 22:52:11 -07:00
config Automatic 'external' port collision correction. If a forwarded port collides with any created VM and is marked to be fixed automatically, then vagrant will choose a new port automatically. 2010-05-27 17:31:36 -07:00
keys updated links on error messages and keys readme to reflect forthcoming windows documentation 2010-03-25 23:07:10 -07:00
lib New wrapper SSH session class to emit exit status as well. Will be used in the future to raise exceptions for bad exit status. For now, works as a drop-in replacement. 2010-05-28 14:19:35 -07:00
templates Primary VM is SSH by default on call to `vagrant ssh` 2010-05-27 23:06:57 -07:00
test New wrapper SSH session class to emit exit status as well. Will be used in the future to raise exceptions for bad exit status. For now, works as a drop-in replacement. 2010-05-28 14:19:35 -07:00
.gitignore fix for uri parsing issues on windows with a small refactor thrown in on the side 2010-03-22 23:49:36 -07:00
Gemfile Environment loads blank VMs for non-created VMs. 2010-05-15 01:34:31 -07:00
LICENSE MIT License 2010-03-07 16:58:24 -08:00
README.md Updated README (slight typos) 2010-05-20 02:32:04 -07:00
Rakefile Upped VirtualBox version requirement to 0.6.2 (unreleased) to force git version 2010-04-29 00:22:07 -07:00
VERSION Incremented version to 0.3.5.dev. 2010-05-21 20:52:56 -07:00
vagrant.gemspec New wrapper SSH session class to emit exit status as well. Will be used in the future to raise exceptions for bad exit status. For now, works as a drop-in replacement. 2010-05-28 14:19:35 -07:00

README.md

Vagrant

Vagrant is a tool for building and distributing virtualized development environments.

By providing automated creation and provisioning of virtual machines using Oracle’s VirtualBox, Vagrant provides the tools to create and configure lightweight, reproducible, and portable virtual environments. For more information, see the part of the getting started guide on ”Why Vagrant?”

Quick Start

First, make sure your development machine has VirtualBox installed. The setup from that point forward is very easy, since Vagrant is simply a rubygem.

sudo gem install vagrant

To build your first virtual environment:

vagrant init
vagrant box add base http://files.vagrantup.com/base.box
vagrant up

Getting Started Guide and Video

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

There is also a fairly short (12 minute) getting started video which explains how to build a fully functional LAMP development environment, which covers a few parts of Vagrant in more detail than the website 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 build
sudo rake install

Contributing to Vagrant

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

bundle install
bundle exec rake

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