The Correct Way to Build Configurable PHP Applications (1)_PHP Tutorial

This article illustrates several ways to create configurable PHP applications. The article also explores the ideal configuration points in an application and seeks a balance between an application that is too configurable and one that is too closed.

If you plan to make your PHP application available to other people or companies, you need to make sure that the program is configurable. At a minimum, allow users to set database logins and passwords in a secure manner so that the material within them is not made public.

This article demonstrates several techniques for storing configuration settings and editing these settings. In addition, the article also provides guidance on which elements need to be made configurable and how to avoid falling into the dilemma of over- or under-configuration.

Configuration using INI files

PHP has built-in support for configuration files. This is accomplished through an initialization file (INI) mechanism such as a php.ini file, where constants such as database connection timeouts or how sessions are stored are defined. If you wish, you can customize the configuration for your application in this php.ini file. To illustrate, I added the following lines of code to the php.ini file.

myapptempdir=foo

I then wrote a small PHP script to read this configuration item, as shown in Listing 1.

Listing 1. ini1.php

<p>＜?php<br>function get_template_directory()<br>{<br>　$v = get_cfg_var( "myapptempdir" );<br>　return ( $v == null ) ? "tempdir" : $v;<br>}<br>echo( get_template_directory()."n" );<br>?＞</p>

When you run this code on the command line, you get the following results:

<p>% php ini1.php<br>foo<br>% </p>

Awesome. But why can't we use the standard INI function to get the value of the myapptempdir configuration item? I did some research and found that in most cases, custom configuration items cannot be obtained using these methods. However, it is accessible using the get_cfg_var function.

To make this method simpler, encapsulate access to the variable in a second function that takes the configuration key name and a default value as parameters, as shown below.

Listing 2. ini2.php

<p>function get_ini_value( $n, $dv )<br>{<br>　$c = get_cfg_var( $n );<br>　return ( $c == null ) ? $dv : $c;<br>}</p><p>function get_template_directory()<br>{<br>　return get_ini_value( "myapptempdir", "tempdir" );<br>} </p>

This is a good overview of how to access INI files, so if There is no need to go to the trouble of changing a large number of functions to use a different mechanism or store the INI file elsewhere.

I do not recommend using INI files for application configuration, for two reasons. First, while this makes it easier to read the INI file, it makes it nearly impossible to write the INI file safely. So this is only suitable for read-only configuration items. Second, the php.ini file is shared across all applications on the server, so I don't think application-specific configuration items should be written in that file.

What do you need to know about INI files? The most important thing is how to reset the include path to add configuration items as shown below.

Listing 3. ini3.php

<p>＜?php<br>echo( ini_get("include_path")."n" );<br>ini_set("include_path",<br>ini_get("include_path").":./mylib" );<br>echo( ini_get("include_path")."n" );<br>?＞ </p>

In this example, I added my local mylib directory to the include path , so you can require PHP files from this directory without adding the path to the require statement.

1

http://www.bkjia.com/PHPjc/446814.htmlwww.bkjia.comtruehttp: //www.bkjia.com/PHPjc/446814.htmlTechArticleThis article illustrates several ways to create configurable PHP applications. The article also explores the ideal configuration points in an application and finds the balance between an application that is too configurable and one that is too closed...