search

xforty / vagrant-drupal

Template repo for a new drupal project built on top of a vagrant vm.
Other
46 stars 11 forks source link

Document creating your own vbox and rebaselining #15

Closed pearcec closed 12 years ago

pearcec commented 12 years ago

At xforty we don't use the dropbox that we provide for demonstration purposes vagrant-drupal. It is our intention that people can clone the repo and make use of it quickly. Ultimately if you adopt using our vagrant-drupal you probably want to have your own vbox. There are two issues here.

  1. How do we use veewee to create our own basebox
  2. How can we use Vagrant to store off updated versions of our basebox. If you run vagrant up it takes chef a while to run through the provision. If we are smart we can have a recipe that provisions most of the default recipes you want without leaving any cruft. So you want apache and squid installed, but not a configuration for local.drupal.conf having around.
dkingofpa commented 12 years ago

There are a ton of gotchas and missteps that could be made by trying to "re-baseline" your base box. There are certain items that are only configurable the first time you run chef-solo. For example, the mysql root password or an apache virtualhost setup.

To avoid future headaches, I suggest not trying to re-baseline. Instead, try to create a base box that has as much as possible installed to save time during chef-solo provisioning later during development. If you have something that needs to be configured for each project, install via chef-solo. Otherwise, install it on your base box. Use veewee to build your own base boxes.

Closing ticket.