Tagged “veewee”

1. End "Works on My Machine" Surprises with Vagrant November 2011

   How many times have the following issues happened on a project you've worked on?

   • Notices (or worse) appeared on production because of a PHP version mismatch between a developer's machine and the production web servers.
   • A new PHP extension or PECL extension had to be installed on production because it was installed in WAMP or MAMP?
   • A team member ran into difficult setting up their local environment and spent many hours stuck on something.
   • Team members didn't set up SSL or Varnish on their local machines and issues had to be caught on a dev server.
   • A team member would like to switch to Homebrew, but can't set aside the many hours to redo their setup until a project is done.
2. Ensuring your Vagrant's box is weatherproof: A quick Veewee tip October 2011

   We'll be doing a screencast series soon on using the Vagrant gem to distribute and manage virtual machines so that your entire team (yes, even Windows folks!) can do development on their local machine with the same software that's on your production Linux servers.Another useful tool in the Vagrant user's arsenal is Veewee. Veewee lets you automate the VirtualBox application to install a full operating system with just the packages you want and need. Veewee does have some built-in validation tools, such as vagrant basebox validate BOXNAME, which will run a set of Cucumber acceptance tests to ensure that the virtual machine should work properly when brought up with Vagrant, as well as with the Chef and Puppet configuration management tools.

See all tags.