<?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 11:28:51 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Lorna Mitchell's Blog: Using an Existing Vagrant Setup for PHP Development]]></title>
      <guid>http://www.phpdeveloper.org/news/17934</guid>
      <link>http://www.phpdeveloper.org/news/17934</link>
      <description><![CDATA[<p>
In <a href="http://www.lornajane.net/posts/2012/using-an-existing-vagrant-setup-for-php-development">this new post</a> to her blog <i>Lorna Mitchell</i> dives into the world of vagrant/puppet/chef and looks at using the tools to automatically create VMs that you can use for PHP development (or testing).
</p>
<blockquote>
I've been hearing great things about <a href="http://puppetlabs.com/">puppet</a>, <a href="http://www.opscode.com/chef/">chef</a>, <a href="http://vagrantup.com/">vagrant</a>, and friends for a while now, but since I work on my own I tend to either develop straight onto my ubuntu machine or grab an appropriate existing VM and use that. So I read about this brave new world of virtualisation but (as with most tools) they can be hard to introduce on your own, and I didn't. [...] Then I went to <a href="http://whiskyweb.co.uk/">WhiskyWeb</a>, which had a hackathon [...] with the shiny new technology all packaged for me, I decided it was time to take a look!
</blockquote>
<p>
She shows you how to get the VM started up using vagrant, pausing the instance and removing it all together (destroy). She also includes the command to directly access the VM via ssh and links to the <a href="http://vagrantup.com/">joind.in project</a> with its sample puppet configuration and Vagrant file.
</p>]]></description>
      <pubDate>Wed, 09 May 2012 10:50:24 -0500</pubDate>
    </item>
  </channel>
</rss>
