On my project I maintain a small "config" file that contains all variables that have unique values based on the hostname that the script is running on. Examples are: the path to ORACLE_HOME, etc. etc.

To keep things organized, don't put anything else in this file.

Care must be taken when switching from dev to production to use the "correct" config file. One trick to help with this is to name the config files like "<hostname>.config" and have the parent code read in $hostname.config

I have a very simple parsing routine that reads each line in the config file, ignores comments lines, and sets a name value pair in a hash. I also set some needed ENV vars too.

In my code I use the values like so:

  my $localvar = $CONFIG{'TEMP_DIR'};
[download]

-------------------------------------
Nothing is too wonderful to be true
-- Michael Faraday