<?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, 09 Jan 2009 22:39:22 -0600</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[devthatweb: Automate the deployment of any PHP project using Capistrano]]></title>
      <guid>http://www.phpdeveloper.org/news/7990</guid>
      <link>http://www.phpdeveloper.org/news/7990</link>
      <description><![CDATA[<p>
On the devthatweb blog, there's <a href="http://devthatweb.com/view/automate-the-deployment-of-any-php-project-using-capistrano">a new post</a> from <i>Pat Nakajima</i> with a recipe for deploying a PHP application with the help of <a href="http://manuals.rubyonrails.com/read/chapter/97#page256">Capistrano</a> (the Ruby on Rails tools for deploying web applications).
</p>
<blockquote>
Recently though, I was working on a PHP project, and I decided that the time had come to rewrite my Mint recipe to allow deployment of any PHP project, totally independent of Rails. I set to work, and I'm happy to share the result.
</blockquote>
<p>
The example makes it a simple matter of using the command "cap deploy:php" to use <a href="http://devthatweb.com/view/automate-the-deployment-of-any-php-project-using-capistrano">the recipe</a> and push out your PHP application.
</p>]]></description>
      <pubDate>Wed, 06 Jun 2007 13:14:00 -0500</pubDate>
    </item>
  </channel>
</rss>
