You might be better off looking at $r->servername in a PerlPostReadRequest handler or something similar, and then setting the db connect value in $r->pnotes so that you don't pollute ENV across all requests.

Even better, run a separate apache server for qa. If you get a bug in there, you run the risk of connecting your qa site to the production database, which can have undesirable consequences. This approach also has the added bonus that you will be able to use Apache::DBI for persistent DB connections, whereas I don't think you can do that with the example you have shown.

In reply to Re: mod_perl2 Apache VirtualHost ENV settings [OT?] by redhotpenguin
in thread mod_perl2 Apache VirtualHost ENV settings [OT?] by graq

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.