info/php-the-right-way
1
0
Fork 0
mirror of https://github.com/codeguy/php-the-right-way.git synced 2025-08-12 08:43:58 +02:00
Code Issues Projects Releases Wiki Activity

Adding more information about vagrant, extracting it into it's own section

Browse Source
This commit is contained in:
Sebastian Goettschkes
2012-12-09 20:52:59 +01:00
parent 19b0d7b6f8
commit 86c0eba961
2 changed files with 22 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
_posts/01-05-01-Windows-Setup.md
View File

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

22
_posts/01-06-01-Vagrant.md Normal file
View File

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