title: using phing to deploy different environments
body: <p>We're using phing to deploy our php application and we got into a little issue with deploying our environments.</p>
  
  <p>We have 2 different production environments (each one with different config files), and a separate testing environment. We don't have an issue with the testing environment, as we have a different branch for the testing environment. The problem is that we're using the same branch for both our production environments.</p>
  
  <p>Anyone has suggestions on how we can deploy into our production environments with different config / setting files? We rather keep the production branch as a single branch, but somehow separate the config files. We use zend framework, and I know about the different section we can have in the config files, but we also have a setting file for phing. </p>
  
  <p>I looked around, but I can't seem to find a way to pass command line arguments to phing. Something like this could be really useful:</p>
  
  <pre><code>  phing -f build.xml production_live1
  </code></pre>