On Dec 11, 2007, at 8:56 AM, Adrian Crum wrote:
I was thinking more along the lines of having some of the system- level configuration options stored in an entity - so we could have a basic system configuration UI. Of course some things could be left out - like the cache settings you mentioned previously.I'll put the idea on the shelf for now.
I'm pretty against having configuration like this in the database... it makes it really difficult to manage overall, largely because revision control is either not there, or done in the database separate from the code revision control, making deployments very error prone because you have to manually keep an eye on these settings in the database and make sure they are up to date.
If you have a config UI it makes it even more difficult to manage because if someone changes something in the UI and someone else writing code makes a corresponding configuration in the file system, when the data is reloaded you might end up with a change loss problem... and that's only one scenario.
-David
smime.p7s
Description: S/MIME cryptographic signature
