Re: [OT] What is 'Good Practice' use of an .ini/.conf file: Database or Active Document?

I think this is like asking the best way to make a bacon butty, everyone has their own opinion.

For my personal preference, everything listed, and unused sections/values explicitly marked with something very obvious, eg "***UNUSED***", that will not be processed as 0, nil, null, the empty string or any other legitimate value.

If its done right, it gives a one file specification and data, everything together and self-documenting db.

The only cogent argument I remember against it is that if it is a public file, it can give "the bad guys" an insight to the internals.

That said, if you ever had to try to maintain or compare Apache config files ... :(

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority". The enemy of (IT) success is complexity.

In the absence of evidence, opinion is indistinguishable from prejudice. Suck that fhit

Comment on Re: [OT] What is 'Good Practice' use of an .ini/.conf file: Database or Active Document?