<?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 16:42:44 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Evan Coury: Environment-specific configuration in Zend Framework 2]]></title>
      <guid>http://www.phpdeveloper.org/news/18249</guid>
      <link>http://www.phpdeveloper.org/news/18249</link>
      <description><![CDATA[<p>
<i>Evan Coury</i> has a new post looking at setting up <a href="http://blog.evan.pro/environment-specific-configuration-in-zend-framework-2">environment specific configurations</a> in a Zend Framework 2 application letting you switch between configs based on an environment variable.
</p>
<blockquote>
So you're all excited to try out ZF2. You <a href="http://blog.evan.pro/getting-started-with-the-zf2-skeleton-and-zfcuser">clone the skeleton, install some modules</a>, maybe even follow <a href="http://akrabat.com/zend-framework-2-tutorial/">Rob Allen's excellent ZF2 tutorial</a>, and finally, start building your application. Now, if you're a former ZF1 user or refugee from another framework, you might be troubled at this point by the fact that, at first glance, ZF2 doesn't appear to take into consideration environment-specific configuration values (e.g., development, testing, staging, production). Luckily, this is not the case!
</blockquote>
<p>
He includes a bit of sample code showing how you can use a simple <a href="http://php.net/getenv">getenv</a> call to pull in the value from an "APPLICATION_ENV" environment variable and put it into an autoload path.
</p>]]></description>
      <pubDate>Thu, 19 Jul 2012 11:36:06 -0500</pubDate>
    </item>
  </channel>
</rss>
