<?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>Mon, 20 May 2013 07:31:14 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Till Klampaeckel's Blog: Deploying PHP applications: PEAR and composer resources for chef]]></title>
      <guid>http://www.phpdeveloper.org/news/17592</guid>
      <link>http://www.phpdeveloper.org/news/17592</link>
      <description><![CDATA[<p>
In a new post to his site <i>Till Klampaeckel</i> shows how to <a href="http://till.klampaeckel.de/blog/archives/180-Deploying-PHP-applications-PEAR-and-composer-resources-for-chef.html">use PEAR and composer resources</a> (two popular PHP package management tools) from inside of a chef deployment script.
</p>
<blockquote>
This is something experimental I have been working on for our chef deployments. So the objective was/is to find a sane way to install PEAR packages and install dependencies with composer.
</blockquote>
<p>
He shows how to set up the configuration script to discover a new PEAR channel, make the chef script not "fail hard" if a command returns a failed response code (as PEAR will do if the channel is already discovered). The "ignore_failure" configuration directive comes in handy for this. He also shows how to implement a <a href="http://wiki.opscode.com/display/chef/Lightweight+Resources+and+Providers+%28LWRP%29">LWRP</a> in chef for both a PEAR and Composer resource. 
</p>
<p>
You can find the code for this and other cookbook examples <a href="https://github.com/till/easybib-cookbooks/tree/master/php/">on his github account</a>.
</p>]]></description>
      <pubDate>Mon, 27 Feb 2012 13:17:57 -0600</pubDate>
    </item>
  </channel>
</rss>
