automate your development environments with vagrant
DESCRIPTION
These are the slides from a lightning talk I gave at a Showclix 'Engibeering' event. The talk described the purpose and usage of Vagrant, a tool for automating the creation and deployment of customized software development environments for projects. * See more of my work at http://www.codehenge.netTRANSCRIPT
Automate Your Build Environment with Vagrant
C. Aaron Coiswww.codehenge.net
@aaroncois
Cause?
• Lack of parity between environments throughout your dev process
• Devs:– Prefer different OSs [Windows/Linux/OSX]– Work on multiple projects– They tinker…– They install things…
Haskell
ErlangC++
Haskell
ErlangC++
Haskell
ErlangC++
Haskell
ErlangC++
Haskell
ErlangC++
So?
• Each application causes system divergence– New libraries– Conflicting versions of languages/frameworks– Different network configs
The Ideal
• Unique development environment for each project
• Identical environments for each developer
…Enter Vagrant
Vagrant
• Leverage virtualization and automated system configuration
• Automatically create and seamlessly manage custom development environments
• Built on– VirtualBox– Chef/Puppet/scripts
Clever Girl…
Keep your usual host dev tools– IDE– Browser
Demo
Resources
• Gareth Rushgrove maintains a nice list of Vagrant base boxes at
http://www.vagrantbox.es
• I have some examples on github:https://github.com/cacois
Thank you
Feel free to contact me:
C. Aaron [email protected] / @aaroncois
https://github.com/cacois
www.codehenge.net