Beefy Boxes and Bandwidth Generously Provided by pair Networks
No such thing as a small change

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 ( #994074=note: print w/replies, xml ) Need Help??

in reply to Refactoring conf-driven app into a module; what to do with the config?

As moritz already pointed out, if the information is static then what you have is a data file. In that event why not embed it into your module somehow?

If the end user is expected to modify the information somehow (DB name, DB host, user, password et. al.) then you should be using a configuration file. YAML, JSON, XML or just a good old fashioned text file with key value pairs is good. Another technique I've seen more than once is to create a file that looks a lot like a Perl module (in fact is) or plain Perl code to be read. Example:

package MyConfig; # # For the record: fixed the following 4 lines since my fingertips dec +ided to do something # other than what my brain was telling them to. s/my/our/ our $datahost=""; our $datauser="user"; our $password="s3cr3t"; our $database="thedata"; 1;
which is then used thusly:
|random handwaving here... use MyConfig; my $host=$MyConfig::datahost; my $user=$MyConfig::datauser; my $pass=$MyConfig::password; my $database=$MyConfig::database; | now do something with it...

Personally for my own uses I use XML files and XML::Simple to load them.

Peter L. Berghold -- Unix Professional
Peter -at- Berghold -dot- Net; AOL IM redcowdawg Yahoo IM: blue_cowdawg

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://994074]
and the monastery is silent...

How do I use this? | Other CB clients
Other Users?
Others making s'mores by the fire in the courtyard of the Monastery: (2)
As of 2018-08-18 01:11 GMT
Find Nodes?
    Voting Booth?
    Asked to put a square peg in a round hole, I would:

    Results (184 votes). Check out past polls.