Planning Your Virtual Machine Use

Video loading...

Join Drupalize.Me to watch this video

Join today and gain instant access to our entire video library.

Log in Sign up
  • 0:05
    with Emma Jane Westby
  • 0:09
    Once you discover the power of provisioning
  • 0:11
    with automated tools such as Chef, or maybe you look into Puppet
  • 0:15
    or Ansible or even shell scripting, you're
  • 0:18
    going to want to wonder why you would ever possibly have only
  • 0:22
    one instance of the Vagrant machine.
  • 0:24
    In this lesson, we're going to talk about the benefits of having
  • 0:28
    a single Vagrant instance, and when it makes
  • 0:32
    sense to have many different machines.
  • 0:35
    First off, let's talk about when to combine all of your projects
Loading ...

Planning Your Virtual Machine Use


Everyone will use Vagrant a little differently. In this lesson, Emma shares some of her strategies for using Vagrant for her personal developer environment.

Lesson Objectives

By the end of this lesson, you will be able to describe how many Vagrant instances you will use, and why.

Lesson Summary

Emma started with one Vagrant instance per project but found that she switches tasks frequently enough that it was a problem--with only 8G RAM, it's hard to have more than one machine running at a time. Although the shut down + startup procedure only takes about five minutes, but it's still dead time. This is especially true as the shut down/start up time doesn't include pulling a fresh copy of the Git repository and updating the database. Emma recommends: grouping your projects with similar requirements into the same Vagrant instance IF you are limited by hardware resources AND you need to switch tasks frequently. Then, as needed, create new vagrant instances if you can justify the split. For example: if you need two different versions of PHP or two different servers (nginx vs. Apache).

Additional resources: