From 86c0eba961d6d2ea834dbd312fe1b7a393355b51 Mon Sep 17 00:00:00 2001 From: Sebastian Goettschkes Date: Sun, 9 Dec 2012 20:52:59 +0100 Subject: [PATCH] Adding more information about vagrant, extracting it into it's own section --- _posts/01-05-01-Windows-Setup.md | 7 ------- _posts/01-06-01-Vagrant.md | 22 ++++++++++++++++++++++ 2 files changed, 22 insertions(+), 7 deletions(-) create mode 100644 _posts/01-06-01-Vagrant.md diff --git a/_posts/01-05-01-Windows-Setup.md b/_posts/01-05-01-Windows-Setup.md index 1cd34ab..c6430bf 100644 --- a/_posts/01-05-01-Windows-Setup.md +++ b/_posts/01-05-01-Windows-Setup.md @@ -17,10 +17,6 @@ If you need to run your production system on Windows then IIS7 will give you the to go, you just need to configure PHP as a handler. For support and additional resources there is a [dedicated area on iis.net][php-iis] for PHP. -Generally running your application on different environment in development and production can lead to strange bugs popping up when you go -live. If you are developing on Windows and deploying to Linux (or anything non-Windows) then you should consider using a Virtual Machine. This -sounds tricky, but using [Vagrant][vagrant] you can set up simple wrappers, then using [Puppet][puppet] or [Chef][chef] you can provision these boxes and share them with your colleagues to ensure you're all working on the same stack. More on this soon. - [php-downloads]: http://windows.php.net [phpmanager]: http://phpmanager.codeplex.com/ [wpi]: http://www.microsoft.com/web/downloads/platform.aspx @@ -28,6 +24,3 @@ sounds tricky, but using [Vagrant][vagrant] you can set up simple wrappers, then [xampp]: http://www.apachefriends.org/en/xampp.html [wamp]: http://www.wampserver.com/ [php-iis]: http://php.iis.net/ -[vagrant]: http://vagrantup.com/ -[puppet]: http://www.puppetlabs.com/ -[chef]: http://www.opscode.com/ diff --git a/_posts/01-06-01-Vagrant.md b/_posts/01-06-01-Vagrant.md new file mode 100644 index 0000000..9f824f8 --- /dev/null +++ b/_posts/01-06-01-Vagrant.md @@ -0,0 +1,22 @@ +--- +isChild: true +--- + +## Vagrant {#vagrant_title} + +Running your application on different environments in development and production can lead to strange bugs +popping up when you go live. It's also tricky to keep different development environments up to date with the same +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. + +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. + +[vagrant]: http://vagrantup.com/ +[puppet]: http://www.puppetlabs.com/ +[chef]: http://www.opscode.com/