News Feed
Sections




News Archive
Looking for more information on how to do PHP the right way? Check out PHP: The Right Way

Vidyut Luther's Blog:
Where do you "define" your environment/global settings?
January 20, 2006 @ 06:44:36

From Vidyut Luther today, there's this new post that asks the question "Where do you 'define' your environment/global settings?"

I was wondering how people handled this situation themselves. I'm personally trying to decide whether my constants be in the class files, or a global configuration file. Right now I have a global.conf.php which contains things like (MySQL login info, include paths, table names).

So, my question is: Is it better to have one big configuration file, or should some things be defined on top of the individual classes ? (CONTACTS_TABLE.. is a clear example). I see pros and cons for both approaches.

He lists out pros and cons for the "one file approach" versus the "multiple specific definitions" method, for example:

  • simple editing vs. easier to manage
  • a single large file vs. multiple small files
  • high memory usage on every page vs. lower memory consumption from loading only what's needed
0 comments voice your opinion now!
define global settings multiple file single large small define global settings multiple file single large small


blog comments powered by Disqus

Similar Posts

Gonzalo Ayuso: Building a Silex application from one Behat/Gherkin feature file

Jeremy Johnstone's Blog: PHP parser for OS X plist XML files

Dave Dash's Blog: symfony and the .htaccess file

Chris Jones' Blog: The Global PHP Community

Nessa's Blog: Using PHP to Display Version Info (I and II)


Community Events





Don't see your event here?
Let us know!


interview install symfony community api release zendserver update package list language library podcast series deployment introduction tips framework laravel opinion

All content copyright, 2014 PHPDeveloper.org :: info@phpdeveloper.org - Powered by the Solar PHP Framework