Comments on: Simple config management for PHP

By: Me

Me — Tue, 23 Feb 2010 14:49:51 +0000

$value = $configManager->getConfig['datasource.host'];

Shouldn’t that be ( ) brackets?

By: sandrar

sandrar — Thu, 10 Sep 2009 13:43:08 +0000

Hi! I was surfing and found your blog post… nice! I love your blog. Cheers! Sandra. R.

By: Simple config management for PHP - Eirik Hoem [ Planet PHP ]

Simple config management for PHP - Eirik Hoem [ Planet PHP ] — Tue, 10 Jun 2008 18:01:05 +0000

[...] 30th 2008 9:32am [-] From: blog.eirikhoem.net [...]

By: Back, (somewhat) rested, and much catching up to do. « Trausch’s Little Home

Thu, 05 Jun 2008 06:51:24 +0000

[...] I’m really going to want to read from the things that will benefit me little. Today I read an article which I could have lived my life without reading, if only because that’s already how I do [...]

By: Aaron Saray

Aaron Saray — Mon, 02 Jun 2008 16:27:32 +0000

This configuration option is nice… but what about times when your configuration has to make a decision? For example, if I’m using the same code base over multiple partner websites, but the name is different, I need to make a choice on what name to display as the global one.

INI files would allow you to have either 1) multiple INI files – kinda code duplication or 2) have them outside of the code base – which may make them naked to versioning software.

I’ve found that I end up using a class with a static ‘get’ method – that creates a new instance of itself in singleton pattern – which performs all of the logic calculations.

Keep up writing!
-aaron

By: Chris Carlson » links for 2008-05-31

Chris Carlson » links for 2008-05-31 — Sat, 31 May 2008 23:32:49 +0000

[...] Simple config management for PHP (tags: php webdesign programming language configuration application classes) 06:32:47 pm on May 31, 2008 | # | [...]

By: Michael Sharman

Michael Sharman — Fri, 30 May 2008 23:53:37 +0000

As a php noob…

Why have the expense of instantiating an object each time for these static variable lookups, why not just include a config file?

require_once “myConfig.inc.php”;

Then just access the vars as normal? If overwriting is a concern you can always prefix with something like:

$config_adminemail = “me@wherever.com”;

By: Lux

Lux — Fri, 30 May 2008 20:33:47 +0000

Looks like my examples didn’t make it through… Let’s try again:

;

…

; */ ?>

By: Lux

Lux — Fri, 30 May 2008 20:32:39 +0000

We use ini files extensively for configuration info in our framework, but one thing to be mindful of if you’re storing sensitive info in there is to make sure it can’t be seen in the browser. You could do something in your config like this:

Deny from all

But we take an extra step I’d recommend taking as well:

1) Make sure the files end in .php
2) Add the following lines at the top and bottom:

;

(Hopefully that renders okay Now if someone requests that in the browser, the site returns a blank screen with just “; ” on it. Hope that helps you out too.

By: Matthew Vines

Matthew Vines — Fri, 30 May 2008 19:45:37 +0000

In response to Jeremy,

That is a great point, and something you should always try to be cognizant of as you set up your we projects. I find that one of the easiest ways to protect config files, whether, ini file format, or xml format, is to give them a .php extension. This way the server parses them as PHP (which ends up looking like a blank file to the browser). But your code doesn’t care what the extension is, as we are just working with a stream to a file, the extension is irrelevant. Only one way to go, but its a viable option for those who are not strong server administrators.