I'm pretty sold on the OO approach, but there are a few additional wrinkles I neglected to mention. I agree that having a perl-based config file is very handy and easy to use. When we do so, we typically want to use info from the machine config inside the app-specific config file. So... 

# In my cgi script...
use My::Config;
my $config = My::Config->new(project => 'GuestBook');

require $config->get('config_path') . "app_config.pl";

# Now, inside app_config.pl, what's the best way to get at the config
# object if I want to use some of the methods?
# Just create another new object? It seems wrong to do it again,
# but I suppose the overhead
# is probably trivial.

# Inside app_config.pl

package My::App;

use My::Config;
our $config = My::Config->new(project => 'GuestBook');

if ( $config->get('env_dev') ){
  # We're in dev, so set the dev passwords.
}

# etc.

[download]

Now, how do you feel about then using the $config object as a package variable to access it in other code that is part of the framework but outside the scope of the original script? Using the code above, I could then do this, right? 


package My::App::Page;

my $db_password = $My::App::config->get('db_password');

[download]

In reply to Re^2: Configuration Best Practices for Web Apps by cbrandtbuffalo
in thread Configuration Best Practices for Web Apps by cbrandtbuffalo

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.