title: my_config.ini vs my_config.php
body: <p>At work we use a .ini file to set variables prior to calling the rest of the framework (I think it goes</p>
  
  <pre><code>function getConfigVars(){
      //read my_config.ini file
      ....
      //call framework
  }
  </code></pre>
  
  <p>and I have always wondered if there was a benefit to doing it that way.</p>
  
  <p>It seems to me that you then have to write access rules to stop people from looking at it from the web and php has to parse it and understand it. </p>
  
  <p>So, why use my_config.ini rather than my_config.php? It is not like anyone should be touching it after it is set up and it seems more convenient to just call the variables and be able to have your IDE auto complete the text wherever you are using the ini variables / parse it for errors.</p>