wokka has asked for the wisdom of the Perl Monks concerning the following question:
I have an application that manages a database of entries used to build a list. It has a fairly detailed config file written in YAML that it loads via $FindBin::Bin. In addition, it has several state tracking files that finds similarly.
Initially, only the one application automatically added to the list, but now a suite of tools has become necessary to do different things with this database beyond simple, automated modification. I've moved all of the shared code to a module, but I'm curious what to do with the config file.
None of the values stored in the configuration are necessary outside of the scope of the module, but I'm not sure that moving it into a __DATA__ section is what's called for, nor am I sure what to do about the state files. Does anyone have any experience with this? What did you do?
|
---|
Replies are listed 'Best First'. | |
---|---|
Re: Refactoring conf-driven app into a module; what to do with the config?
by moritz (Cardinal) on Sep 17, 2012 at 18:27 UTC | |
by wokka (Acolyte) on Sep 17, 2012 at 19:07 UTC | |
by moritz (Cardinal) on Sep 18, 2012 at 04:26 UTC | |
by Anonymous Monk on Sep 17, 2012 at 19:32 UTC | |
Re: Refactoring conf-driven app into a module; what to do with the config?
by blue_cowdawg (Monsignor) on Sep 17, 2012 at 18:36 UTC |
Back to
Seekers of Perl Wisdom