how to store configurations for php app -- xml or ini or db [closed]

Question

I've got an app written in PHP, and there are a number of configurable variables. We're implementing a feature where the user can create sets of configurations and easily switch between them. How should I store my configs? as XML? in a .ini file? in multiple .ini files? in a db?

What's going to provide the most flexibility if we add fields down the road? Coding convenience?

If I use a db, I'll have to use a separate one from the app's main one for reasons that aren't worth going into, which has made me shy away from that. (Also, we're using .mdb files for our db.)

I've been going down the xml route, but I'm having problems with adding and editing configs using SimpleXML. Also, the app has to be compatible with php 5.1.6, and I'm a little nervous about some of the functionality.

Never really dealt with creating custom ini files....

A small clarification: the users won't touch the files -- they're non-techie. So setting up the initial files will be done by us, but then we're writing a tool that is going to writie out their configuration(s) to whatever format we choose.

Answer 1

I would store the configurations items in a PHP file. This is the most flexible method I have used.

$config['website_url'] = 'google.com';

I then have the following file structure

- config/development
- config/production

I have a constant defined early in the software named IN_PRODUCTION, when this is TRUE it loads up the production configuration items and vice versa.

This is simple and easily maintainable.

-Mathew

Answer 2

Storing the settings for one DB in a different DB does not make much sense, IMO.

I would choose either an ini file, an xml file, or a php file, as proposed by jmucchiello. Each option has it's pros and cons. As for xml versus ini, xml offers more flexibility but is more difficult to maintain (less readable). If your needs are covered by ini, stick with the simpler solution. Use xml only if you need more than ini files can offer you.

As for the php solution, I would rate the readability somewhere between ini and xml, but it would be more difficult to save the current settings. So as much as I like the approach, for your current scenarion I would not recommend it.