Another reason to separate out your databse connection info (and my primary reason) is code distribution. If you release your code to outsiders (whether business partners or under a Free/Open Source license), do you really want to lose sleep wondering whether you remembered to remove the password for your private database each time? Do you want that information available in the CVS archive? Not likely...

And then there's standardization. FHS says that all system-wide application configuration data belongs under /etc and I tend to agree with it. Life is so much easier for admins when everything puts its settings in /etc/appname (one config file) or /etc/appname/* (multiple config files).

In reply to Re: Possible CGI/database security issue? by dsheroh
in thread Possible CGI/database security issue? by mephit

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.