This is not a Perl question, per se... but I need to implement a solution for our company's internal home-grown apps, almost all of which are in Perl.
These programs all need to store configuration information—user preferences, user access restrictions, parameters by which to access this database or that, etc. Currently, these apps store their configuration in a hodgepodge of different ways: Most of them have their config parameters hardcoded into them, or hardcoded into a library; some use config files, some use database tables.
I'd like to unify and simplify this. I'd like to have one place on our network where applications can query and update their configuration settings, and where admins can change settings. But how?
A configuration file in a central location would be simple, but then anyone could read it, could see how to connect to the databases, etc. And where to put it?
But what's the alternative? Some dedicated configuration server that responds to SOAP queries over SSL?
In reply to Where to store configuration information? by Sue D. Nymme
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |