[RESOLVED] config file for database connections and common paths

gwerner

I know this question has been asked, but I'm not finding any decent answers. I'm going back through various components and making sure I'm doing things correctly.

What is the better approach to handling a config file? Is it just a matter of preference, or is there best way? I've seen my method below, arrays, using define for everything and parse ini file.

I'm currently including a config file in the index.php page. The config file would reside outside the public_html directory. It looks like:

// database credentials
$dbhost = 'localhost';
$dbport = 3306;
$dbusername = 'root';
$dbuserpassword = 'root';
$default_dbname = 'mydb';

// setting up the web root and server root for
$thisFile = str_replace('\\', '/', __FILE__);
$docRoot = $_SERVER['DOCUMENT_ROOT'];

$webRoot = str_replace(array($docRoot, 'assets/config.php'), '', $thisFile);
$srvRoot = str_replace('assets/config.php', '', $thisFile);
$directory = substr($_SERVER['PHP_SELF'], 0, strrpos($_SERVER['PHP_SELF'], "/"));

define('WEB_ROOT', $webRoot);
define('SRV_ROOT', $srvRoot);

define("LIBRARY_PATH", realpath(dirname(__FILE__) . '/library'));
define("TEMPLATES_PATH", realpath(dirname(__FILE__) . '/templates'));

// category and product images
define('CATEGORY_IMAGE_DIR', 'i/category/');
define('PRODUCT_IMAGE_DIR',  'i/product/');

NogDog

I think part of the answer may be who the intended users will be for that config file. If you are only expecting reasonably proficient PHP users to be changing it, then anything reasonably logical and commented will probably work (not to say some patterns won't be better, though). But if it's something general users without any PHP knowledge to speak of may need to modify, something like a parse_ini_file() config file might be simpler and more consistent for them to edit.

define()-ing constants has the advantage that they can't be accidentally overwritten, and are available in any scope.

An approach you've not mentioned might be to use the "Registry" OOP pattern, putting such config items into such a Registry object which can then be accessed by any part of your code.

gwerner

Thanks for the reply. I didn't mention that last one, because it is above my skill level right now. You are right though, that it is a good way to do from what I've been reading. I'm in the process of getting more familiar with OOP, but just on a basic level right now.

From what I've been reading the ini method seems to be the option most people favor. Essentially for the reason you stated. But, it seems like a lot of personal preference comes into play on most of the options.

Currently I'm the only user. I basically play the role of designer and developer. I want to learn the best way to things, so if down the road I start working with a team I'm familiar with and know how to execute best practices. I also figured what I'm doing is wrong, since it's an older method and wanted to ask so I can stay current.