Presented by Justin Carmony / @JustinCarmony
Slides split up into multiple sections.
Slides both vertical and horizontal.
Nginx - Apache - PHP-FPM - PHP 5.4 (new sites)
PHP 5.3 (legacy tools) - MySQL - MongoDB - Redis
Beanstalkd - Memcached
Using Vagrant, they were able to setup our complex environment on their own in an hour while the other half of our team were sleeping on the other side of the world.
Open up your terminal and run the following:
$ mkdir vagrant_test
$ cd vagrant_test
$ vagrant init precise32 http://files.vagrantup.com/precise32.box
$ vagrant up
What happens when you type: vagrant up
Vagrantfile
The Vagrantfile contains configurations in ruby for:
The Provider will:
The Provisioner (i.e. Puppet, Chef, Salt, Ansible, etc) will:
In our Demo we'll use:
Available Provisioners: Puppet, Chef, Salt, Ansible, Shell
Sometimes you want to allow your team to configure parts of your vagrant project.
Things to configure:
config/prefs.rb
#!/usr/bin/env ruby
$config_source_dir = "/Users/jcarmony/git/demo"
$config_base_box = "precise64"
Vagrantfile
# -*- mode: ruby -*-
# vi: set ft=ruby :
load "config/prefs.rb"
Vagrant has the website http://www.vagrantbox.es/
A couple of things to keep in mind:
vagrant ssh
command.vagrant reload
vagrant provision
vagrant destory
and then vagrant up
<shameless_plug>
BTW, We're Hiring a DevOps position at
Deseret Digital Media, so email me if interested.
</shameless_plug>