Hi John
I don't know how complicated your config gets, but you may want to try incorporating my module Config::Loader Config::Merge, which will allow you to:
- store your data in any of XML, YAML, JSON, INI, Perl, Config::Any
- break your data up into separate files in a config directory tree, for easier maintenance
- have a defined policy for overriding data locally, eg for working safely in dev vs in production
Clint
Update: Updated the module name to reflect its new name | [reply] |
The config is fairly simple at this point. Just a few settings plus dsn's for Application state and Session state managers, as well as a dsn for your application itself (i.e. Class::DBI or DBIx::Class).
Since the Apache2::ASP::GlobalConfig and Apache2::ASP::Config classes are subclassable, one could simply subclass one or the other (depending) to add any desired features (such as a Config::Loader facade).
Thanks for taking a look.
| [reply] |