I have a situation where there's two scripts.
- The main core of the code which is PHP based.
- A perl script which is called by the mail server for parsing incoming mail.
Both of these scripts require database access to the same database.
Previously the solution would be to have two separate files both containing effectively the same information. This is less than ideal, nobody wants settings in two places.
Some have suggested using SETENV with apache, however although this would work fine for the PHP aspect, it wouldn’t work for the perl script as it’s not called via apache.
Some have suggested using ini files, then using parse_ini_file for php, and the ini parser module in perl. My problem with this was that because ini files read as plain text, it becomes a security problem. It is argued that you could deny access using apache’s “.htaccess”, or put the file outside of the web directory (usually public_html). I didn’t think this was suitable.
After some thought, and a little assistance I propose the following solution:
$db_type = ‘mysql’;
$db_host = ‘localhost’;
$db_name = ”;
$db_user = ”;
$db_pass = ”;
Hey presto, we now have 1 settings file that works for both perl and PHP.
_Note: If you’re using strict in perl, you’ll need to define the variables before you include the settings file, otherwise it will complain.
The problem is that php won’t evaluate the code, so we need to create another file, that will read the settings and evaluate them for use with PHP.
$c = file_get_contents(‘settings.pl’);
Problem solved. Enjoy!
Update: After some discussion it was suggested that another way would be to create an ini file, and simply rename it to a file that has a handler in your httpd (such as .pl or .cgi NOT .php as PHP would render it as plain text), then in perl you can use the parser such as Config::INI to read the file and in PHP use parse_ini_file(). The obvious downside to this is the additional overheads that the above method simply does not have. If you have a large amount of settings, it might be worth it.