<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Fri, 24 May 2013 06:38:23 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Chris Hartjes' Blog: Build PHP 5.4 on CentOS With Vagrant]]></title>
      <guid>http://www.phpdeveloper.org/news/17820</guid>
      <link>http://www.phpdeveloper.org/news/17820</link>
      <description><![CDATA[<p>
In a new post to his blog <i>Chris Hartjes</i> shows you how to get <a href="http://www.littlehart.net/atthekeyboard/2012/04/15/build-php-54-on-centos-with-vagrant/">PHP 5.4 installed on a CentOS machine (virtual machine) with the help of Vagrant.
</p>
<blockquote>
I like the idea of using <a href="http://vagrantup.com/">Vagrant</a> to create virtual machines for my development work. Doing things this way I think keeps the host machine cleaner and allows you the ability to distribute those VM's to other people as well. My old boss Ben Ramsey did a very informative post on <a href="http://benramsey.com/blog/2012/03/build-php-54-on-centos-62/">getting PHP 5.4 configured on CentOS</a> so I decided to one-up him by taking his instructions and creating a <a href="http://puppetlabs.com/">Puppet</a> manifest so you could do this using Vagrant or on any server that you can provision using Puppet.
</blockquote>
<p>
He example is based off of <a href="http://www.vagrantbox.es/37/">the publiclly available Vagrant setup</a> and provides the contents of the Vagrantfile that he uses to set up the machine. From there, Puppet takes over and uses his configuration (also included) to set up things like the Apache server, some configurations for it, a list of PHP extensions and, of course, PHP itself.
</p>]]></description>
      <pubDate>Mon, 16 Apr 2012 10:02:02 -0500</pubDate>
    </item>
  </channel>
</rss>
