<?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 12:49:11 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Till's Blog: Managing software deployments of your PHP applications II]]></title>
      <guid>http://www.phpdeveloper.org/news/13201</guid>
      <link>http://www.phpdeveloper.org/news/13201</link>
      <description><![CDATA[<p>
In <a href="http://till.klampaeckel.de/blog/archives/53-Managing-software-deployments-of-your-PHP-applications-II.html">this new post</a> to his blog today <i>Till</i> continues his look at deploying PHP applications with various tools. This time his focus is on <a href="http://www.capify.org/index.php/Capistrano">Capistrano</a>.
</p>
<blockquote>
In <a href="http://till.klampaeckel.de/blog/archives/11-Managing-software-deployments-of-your-PHP-applications-I.html">Part I</a>, I talked about my approach to deploying a website and I offered pear and subversion as solutions to the problem. To briefly elaborate on my subversion part, I want to share the following Capistrano recipe with you.
</blockquote>
<p>
He shows how to set up a sample "capfile" with the commands to perform for his deployment - checking out a release and, using a symlink to change the location, deploy the latest version of the site. He briefly mentions some chaining the tool allows.
</p>]]></description>
      <pubDate>Thu, 10 Sep 2009 11:21:29 -0500</pubDate>
    </item>
  </channel>
</rss>
