Very little has changed from Shawn's original repo, but I've done my best to update things to the current standards of Vagrant and Chef. The tutorial will be modified to reflect changes, but here are some of the bigger ones.
Rather than submodules to manage 3rd party cookbooks, I've opted to use Librarian-Chef instead. So don't put anything in chef/cookbooks! That is now taken care of by librarian. Custom cookbooks go in chef/application-cookbooks and will need to be added to the Cheffile.
I've also added Vagrant-Librarian-Chef to automatically fetch and update cookbooks from Vagrant and Vagrant Omnibus to keep Chef up to date and working correctly.
Very little has changed other than some small syntax changes and the calls to the added Vagrant plugins. I've taken the liberty of changing the box as well and pointing it to a box I made myself. It's just this box with the RubyGem version moved back to 1.8.25.
Why? Because reasons. I'd advise you make your own with VeeWee to prevent those crazy Ruby guys from messing up your environment. Phil concurs and even has a pretty slick tutorial on the subject.
Everything that one needs to create development environments with Vagrant and Chef.
This repo is very much a work in progress. There are many things that can be improved. Annotations were made in comment form within the example Vagrantfile, regarding room for improvement. Issues and pull-requests are encouraged.
- LAMP (PHP 5.4)
- Git
- Composer
- PHPUnit
- automatic MySQL database creation
- automatic apache vhost creation
- other cookbooks and ready for love (ElasticSearch)
These instructions are merely one way to use these tools. I'm presenting them because I feel that they're both reasonable and simple.
These are instructions for creating a development environment utilizing Vagrant for virtual-machine management and Chef for installing and configuring software.
You would install this individually into each site repo. When working on a site, you'd bring up the server. When you're done, you suspend it. I repeat. Each individual site repo has its own virtual-machine that is brought up when you're working on that specific site, and then suspended when you're done.
This should work on any Windows, OSX, or Linux box.
(DO NOT INSTALL FROM PACKAGE MANAGER) If you do install virtualbox, vagrant or chef from package managers then expect pain.
-
Make sure gem -v reads 1.x because 2.x breaks things due to Chef changes
-
Add this repository to yours.
$ cd mysite
$ git submodule add git@github.com:WMeldon/vagrant-chef.git
-
Update the submodules within the submodule. (inception)This is no longer needed because of Librarian-Chef. Just vagrant up and you're good to go!$ git submodule update --init --recursive -
Copy an example Vagrantfile to your project's root.
$ cp vagrant-chef/vagrant/vagrantfiles/Vagrantfile .
-
Read the Vagrant file and modify where appropriate for your project.
-
Add this entry to hosts file
10.10.10.10 app.local
$ vagrant up
Wait until Vagrant / Chef are done. Then, in your browser hit http://app.local.
You have the choice of either... suspending the application (takes a small bit more disk space). Recommended
$ vagrant suspend
or.. you can halt the box. (saves like 200meg?) But, because next time you start it up again it'll take a long time.
$ vagrant halt
If configurations change you can simply run:
$ vagrant reload
It will then apply your changes to the Vagrantfile or cookbooks.
Ok, it's not really that painful in exchange for what you get from it. I add these aliases to my shell script's initialization file for ease. You might like them, too.
alias vl="VBoxManage list runningvms"
alias vu="vagrant up"
alias vd="vagrant suspend"
alias vr="vagrant reload"
alias vs="vagrant ssh"
alias ga="git add ."
alias gc="git commit -a"
alias gp="git push"
There is a known Mac issue with VirtualBox crashing your VMs. Here are more details and the solution.
I've made many annotations of issues in the Vagrantfile example, each could use a solution.
Trying to install this on your system and reporting back any issues that you've had with instructions listed would be a huge help.
Know a bit about Vagrant / Chef and want to complain that something could be done better? Please open an issue.
I decided to make this fork to get things up to date (a near impossible task in the DevOps world). That said, I'm make no guarantees and am far from an expert. But I thought this might be helpful to someone in a similar position.
Thanks for the excellent work Shawn