From 239a4cd54c74261d458eb62eb42eb7371dab69f5 Mon Sep 17 00:00:00 2001 From: Matthias Glaub Date: Wed, 22 Oct 2014 23:44:54 +0200 Subject: [PATCH] introduce virtualization section --- _posts/13-01-01-Virtualization.md | 14 ++++++++++++++ .../{01-06-01-Vagrant.md => 13-02-02-Vagrant.md} | 10 +++------- _posts/{01-07-01-Docker.md => 13-03-03-Docker.md} | 0 .../{13-01-01-Caching.md => 14-01-01-Caching.md} | 0 ...ytecode-Cache.md => 14-02-01-Bytecode-Cache.md} | 0 ...bject-Caching.md => 14-03-01-Object-Caching.md} | 0 ...14-01-01-Resources.md => 15-01-01-Resources.md} | 0 ...-02-01-Frameworks.md => 15-02-01-Frameworks.md} | 0 ...-03-01-Components.md => 15-03-01-Components.md} | 0 _posts/{14-04-01-Books.md => 15-04-01-Books.md} | 0 ...15-01-01-Community.md => 16-01-01-Community.md} | 0 _posts/{16-01-01-PHPDoc.md => 17-01-01-PHPDoc.md} | 0 12 files changed, 17 insertions(+), 7 deletions(-) create mode 100644 _posts/13-01-01-Virtualization.md rename _posts/{01-06-01-Vagrant.md => 13-02-02-Vagrant.md} (72%) rename _posts/{01-07-01-Docker.md => 13-03-03-Docker.md} (100%) rename _posts/{13-01-01-Caching.md => 14-01-01-Caching.md} (100%) rename _posts/{13-02-01-Bytecode-Cache.md => 14-02-01-Bytecode-Cache.md} (100%) rename _posts/{13-03-01-Object-Caching.md => 14-03-01-Object-Caching.md} (100%) rename _posts/{14-01-01-Resources.md => 15-01-01-Resources.md} (100%) rename _posts/{14-02-01-Frameworks.md => 15-02-01-Frameworks.md} (100%) rename _posts/{14-03-01-Components.md => 15-03-01-Components.md} (100%) rename _posts/{14-04-01-Books.md => 15-04-01-Books.md} (100%) rename _posts/{15-01-01-Community.md => 16-01-01-Community.md} (100%) rename _posts/{16-01-01-PHPDoc.md => 17-01-01-PHPDoc.md} (100%) diff --git a/_posts/13-01-01-Virtualization.md b/_posts/13-01-01-Virtualization.md new file mode 100644 index 0000000..8b75a99 --- /dev/null +++ b/_posts/13-01-01-Virtualization.md @@ -0,0 +1,14 @@ +--- +anchor: virtualization +--- + +# Virtualization + +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 beside the widely known virtualization environments like VMware or VirtualBox, there are +additional tools that may help you setting up a virtual environment in a vew easy steps. diff --git a/_posts/01-06-01-Vagrant.md b/_posts/13-02-02-Vagrant.md similarity index 72% rename from _posts/01-06-01-Vagrant.md rename to _posts/13-02-02-Vagrant.md index 54a1778..eb3114f 100644 --- a/_posts/01-06-01-Vagrant.md +++ b/_posts/13-02-02-Vagrant.md @@ -5,13 +5,9 @@ anchor: vagrant ## 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 by using [Vagrant][vagrant] you can set up a simple -virtual machine with only a few steps. These base boxes can then be set up manually, or you can use "provisioning" +[Vagrant][vagrant] helps you building your virtual boxes on top of the known virtual environments and will configure +these environments based on a single configuration file. +These boxes can 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 diff --git a/_posts/01-07-01-Docker.md b/_posts/13-03-03-Docker.md similarity index 100% rename from _posts/01-07-01-Docker.md rename to _posts/13-03-03-Docker.md diff --git a/_posts/13-01-01-Caching.md b/_posts/14-01-01-Caching.md similarity index 100% rename from _posts/13-01-01-Caching.md rename to _posts/14-01-01-Caching.md diff --git a/_posts/13-02-01-Bytecode-Cache.md b/_posts/14-02-01-Bytecode-Cache.md similarity index 100% rename from _posts/13-02-01-Bytecode-Cache.md rename to _posts/14-02-01-Bytecode-Cache.md diff --git a/_posts/13-03-01-Object-Caching.md b/_posts/14-03-01-Object-Caching.md similarity index 100% rename from _posts/13-03-01-Object-Caching.md rename to _posts/14-03-01-Object-Caching.md diff --git a/_posts/14-01-01-Resources.md b/_posts/15-01-01-Resources.md similarity index 100% rename from _posts/14-01-01-Resources.md rename to _posts/15-01-01-Resources.md diff --git a/_posts/14-02-01-Frameworks.md b/_posts/15-02-01-Frameworks.md similarity index 100% rename from _posts/14-02-01-Frameworks.md rename to _posts/15-02-01-Frameworks.md diff --git a/_posts/14-03-01-Components.md b/_posts/15-03-01-Components.md similarity index 100% rename from _posts/14-03-01-Components.md rename to _posts/15-03-01-Components.md diff --git a/_posts/14-04-01-Books.md b/_posts/15-04-01-Books.md similarity index 100% rename from _posts/14-04-01-Books.md rename to _posts/15-04-01-Books.md diff --git a/_posts/15-01-01-Community.md b/_posts/16-01-01-Community.md similarity index 100% rename from _posts/15-01-01-Community.md rename to _posts/16-01-01-Community.md diff --git a/_posts/16-01-01-PHPDoc.md b/_posts/17-01-01-PHPDoc.md similarity index 100% rename from _posts/16-01-01-PHPDoc.md rename to _posts/17-01-01-PHPDoc.md