Re: Config File Shuffle

An example of these config files would help a lot, as would the application you're writing this configuration process for. Along with an XY problem, you might be suffering from a lack of YAGNI.

My criteria for good software:

Does it work?
Can someone else come in, make a change, and be reasonably certain no bugs were introduced?

Comment on Re: Config File Shuffle

Replies are listed 'Best First'.
Re^2: Config File Shuffle by mantadin (Beadle) on Apr 24, 2006 at 18:33 UTC
Supposed, we got the YAGNI case, and all you need is all config vars can be set in the config file and the command line the command line will have the highest priority the user can set the config file location at the command line In that case, you could do it like this: `use Getopt::Std; my %opts; getopts( 'dhc:', \%opts ); # usw, -c for cfg-file $opts{'c'} and $opts{'c'} !~ m{^/([\w\.]+/)[\w\.]+$} and &usage; my $cfg = $opts{'c'} ? $opts{'c'} : '/default/path/to.conf'; open CFG, '<'.$cfg or die; while(<CFG>) { # do sth like ... /^\s(.?)\s: (.*)$/; $cfg{ $1 } = $2; } foreach (keys %cfg) { $opts{$_} and $cfg{$_} = $opts{$_}; }` [download] You can do this "overriding" as many times you like, using a list of config file locations. The script would eat one file after another, starting with the "weakest", most global one, and finishing with the command line options. The overriding process could be done in the manner indicated in the code above.	[reply] [d/l]

Replies are listed 'Best First'.

Re^2: Config File Shuffle
by mantadin (Beadle) on Apr 24, 2006 at 18:33 UTC

all config vars can be set in the config file and the command line
the command line will have the highest priority
the user can set the config file location at the command line

use Getopt::Std;
my %opts;

getopts( 'dhc:', \%opts );      # usw, -c for cfg-file
$opts{'c'} and $opts{'c'} !~ m{^/([\w\.]+/)*[\w\.]+$} and &usage;

my $cfg = $opts{'c'} ? $opts{'c'} : '/default/path/to.conf';

open CFG, '<'.$cfg or die;
while(<CFG>) {
   # do sth like ...
   /^\s*(.*?)\s*: (.*)$/;  
   $cfg{ $1 } = $2;
}
foreach (keys %cfg) {
   $opts{$_} and $cfg{$_} = $opts{$_};
}
[download]

You can do this "overriding" as many times you like, using a list of config file locations. The script would eat one file after another, starting with the "weakest", most global one, and finishing with the command line options.

The overriding process could be done in the manner indicated in the code above.

[reply]
[d/l]