Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Easing the building of vagrant boxes

Fetching latest commit…

Octocat-spinner-32-eaf2f5

Cannot retrieve the latest commit at this time

Octocat-spinner-32 .bundle
Octocat-spinner-32 bin
Octocat-spinner-32 doc
Octocat-spinner-32 lib
Octocat-spinner-32 templates
Octocat-spinner-32 test
Octocat-spinner-32 validation
Octocat-spinner-32 .gitignore
Octocat-spinner-32 .rvmrc
Octocat-spinner-32 Gemfile
Octocat-spinner-32 License
Octocat-spinner-32 README.md
Octocat-spinner-32 Rakefile
Octocat-spinner-32 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 built. 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 progress)

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 definition.rb

Something went wrong with that request. Please try again.