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

Alvaro Videla's Blog: Integrating Facebook Hive with Symfony

Debuggable Blog: Two CakePHP Tricks

Nexen.net: Elephpants, 2008 generation

Rob Allen: Creating a zip file with PHP’s ZipArchive

Chris Hartjes' Blog: Handling Multiple Environments In Your PHP Application


Community Events





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


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

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