Doing some improvements to the vagrant section as suggested by @philsturgeon

This commit is contained in:
Sebastian Goettschkes
2012-12-10 10:22:56 +01:00
parent 86c0eba961
commit 871b53f2c7

View File

@@ -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.