Associated Project(s)

Using Vagrant and Chef to manage your Development Environment

Using tools such as Vagrant and Chef it is possible to ensure that everyone in your team, from design to development, from testing to deployment are using the same environment for their work. This makes it easier to manage and scale the whole process. In this screencast we show you how to get started.

Vagrant is a tool for building complete development environments, sandboxed in a virtual machine. It helps enforce good practices by encouraging the use of automation so that development environments are as close to production as possible.

Chef models IT infrastructure and application delivery as code, giving you the power and flexibility to deliver what your customer wants more quickly and more reliably. It is built to address the hard infrastructure challenges faced by modern developers and IT Pros.

In this screencast we show how to get started with Vagrant and Puppet to create a simple web application development environment. It will show you:

  • How to install Vagrant
  • How to create a Linux based guest virtual machine for development and testing using Vagrant and Hyper-V
  • Use a shared drive between the host and the guest to manage application and configuration data
  • Use version control to share application and configuration data between team members
  • Use Chef to provision the virtual machine
  • Build a simple Hello World web applications

3 thoughts on “Using Vagrant and Chef to manage your Development Environment

  1. It’s great that ms open tech is getting involved in chef community, but:
    – screencast – would be better with real voice instead of tooltips and fake keyboard typing
    – usually windows users are developing windows apps – so will you provide such video with windows guest instead of linux?

    • I do agree that voice is better than screen recording, but perfect is the enemy of good, right? With luck I’ll add voice at a later date.

      As for addressing Windows instead of Linux I agree we need to do both, and in fact both are supported. The modern IT landscape is a mixed one and so here at MS Open Tech we are all about interoperability. The good news is that if you start with a Vagrant Windows Box rather than a Linux one the steps are pretty much identical. If you want to give it a go then you can find details on how to get a Windows box on our Vagrant page here on this site (Projects -> DevOps -> Vagrant).

  2. “In this screencast we show how to get started with Vagrant and Puppet” – possibly fix this in the blog post 😉