Easing the building of vagrant boxes
Перейти к файлу
Patrick Debois 06f93ae0e2 Merge pull request #393 from gregsymons/upstream_integration
Add missing keyups to QWERTY and KillX
2012-10-03 02:43:31 -07:00
bin
doc
lib Add missing keyups to QWERTY and KillX 2012-10-02 17:32:26 -05:00
templates Added templates for Debian 6.0.6. 2012-10-02 20:50:52 -05:00
test
validation
.gitignore
.rvmrc
Gemfile
License
README.md
Rakefile
veewee.gemspec

README.md

VeeWee: the tool to easily build vagrant base boxes or kvm,virtualbox and fusion images

Vagrant is a great tool to test new things or changes in a virtual machine(Virtualbox) using either chef or puppet. The first step is to download an existing 'base box'. I believe this scares a lot of people as they don't know who or how this box was build. Therefore lots of people end up first building their own base box to use with vagrant.

Besides building Vagrant boxes, veewee can also be used for:

  • create vmware (fusion), kvm virtual machines
  • interact with with those vms (up, destroy, halt, ssh)
  • export them : OVA for fusion, IMG for KVM and ovf for virtualbox

Before you start read through:

Depending on how you want to use veewee, read through one of the following guides: (work in progres)

You can also look at the more detailed pages on each subject in the documentation directory

People have reported good experiences, why don't you give it a try?

If you have a setup working, share your 'definition' with me. That would be fun!

IDEAS:

  • Now you integrate this with your CI build to create a daily basebox

[whren - 2012/04/12]

See use of pre_postinstall_file in defition.rb