Go to file
Mitchell Hashimoto f2636355c1 `vagrant init` command. Used for initializing directories with vagrant. 2010-02-12 00:11:49 -08:00
bin Move all commands to the Vagrant::Command class. Document all commands. 2010-02-10 13:46:22 -08:00
config Get rid of "VAGRANT_ENV" since that was just a hack. Log output location configurable now. 2010-02-10 13:59:25 -08:00
lib `vagrant init` command. Used for initializing directories with vagrant. 2010-02-12 00:11:49 -08:00
script And then God said unto thee, "You shall be named Vagrant." 2010-02-09 23:08:23 -08:00
templates `vagrant init` command. Used for initializing directories with vagrant. 2010-02-11 00:51:21 -08:00
test `vagrant init` command. Used for initializing directories with vagrant. 2010-02-11 00:51:21 -08:00
.gitignore `vagrant init` command. Used for initializing directories with vagrant. 2010-02-11 00:51:21 -08:00
Gemfile Provisioning now generates a DNA JSON file and uploads it to the /tmp directory for use. Fixed some issues with SCPing. 2010-02-09 18:16:19 -08:00
README.md One more reference to "Hobo" 2010-02-09 23:13:16 -08:00
Rakefile And then God said unto thee, "You shall be named Vagrant." 2010-02-09 23:08:23 -08:00
VERSION Version bump to 0.0.0 2010-01-30 22:05:51 -08:00

README.md

Vagrant

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
rake

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