Skip to content


Subversion checkout URL

You can clone with
Download ZIP
Browse files

Doing some improvements to the vagrant section as suggested by @phils…

  • Loading branch information...
commit 871b53f2c72473a8b751f7ac1f7e4ad3eee416c5 1 parent 86c0eba
@Sgoettschkes authored
Showing with 5 additions and 3 deletions.
  1. +5 −3 _posts/
8 _posts/
@@ -10,9 +10,11 @@ version for all libraries used when working with a team of developers.
If you are developing on Windows and deploying to Linux (or anything non-Windows) or are developing in a team, you
should consider using a virtual machine. This sounds tricky, but using [Vagrant][vagrant] you can set up a simple
-virtual machine with only a few steps. This so called "base boxes" can then be set up with different software
-using either [Puppet][puppet] or [Chef][chef] (This is called provisioning). If you share those setup files with your
-colleagues you can ensure you're all working on the same stack.
+virtual machine with only a few steps. These base boxes can then be set up manually, or you can use "provisioning"
+software such as [Puppet][puppet] or [Chef][chef] to do this for you. Provisioning the base box is a great way to
+ensure that multiple boxes are set up in an identical fashion and removes the need for you to maintain complicated
+"set up" command lists. You can also "destroy" your base box and recreate it without many manual steps, making it
+easy to create a "fresh" installation.
Vagrant creates shared folders used to share your code between your host and your virtual machine, meaning you can
create and edit your files on your host machine and then run the code inside your virtual machine.

0 comments on commit 871b53f

Please sign in to comment.
Something went wrong with that request. Please try again.