<?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>Sat, 25 May 2013 03:26:31 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Benjamin Eberlei's Blog: Application Lifecycle Management & Deployment with PEAR & PHAR (revisited)]]></title>
      <guid>http://www.phpdeveloper.org/news/13858</guid>
      <link>http://www.phpdeveloper.org/news/13858</link>
      <description><![CDATA[<p>
In <a href="http://www.whitewashing.de/blog/articles/125">a recent post</a> to his blog <i>Benjamin Eberlei</i> looks at how PEAR and PHAR can affect the lifecycle of the development of your application following some of the feedback he got from a <a href="http://www.whitewashing.de/blog/articles/123">previous article</a> on the same topic. In this revised version he talks about the open source project he's started, <a href="http://github.com/beberlei/pearanha">Pearanha</a>, to bundle all of these ideas together.
</p>
<blockquote>
First of all, yes the presented solution was somewhat complex, partly because it is still a proposed idea and definitely up for optimizations. However I am still very convinced of my approach, something I should discuss in more detail.
</blockquote>
<p>
He mentions some of the downfalls that PHP applications have had up until now as far as ease of deployment and the maintaining of dependencies. Most of the suggested solutions aren't optimal, so a system using the PEAR installer would have to overcome some of them and keep it simple to use. <i>Benjamin</i> has taken the PEAR installer and laid his new <a href="http://github.com/beberlei/pearanha">Pearanha</a> tool on top of it to help you create custom PEAR installer scripts.
</p>]]></description>
      <pubDate>Mon, 18 Jan 2010 09:25:05 -0600</pubDate>
    </item>
  </channel>
</rss>
