Run two apaches on the box, like merlyn said. (Actually, two swarms of apaches, but you get my drift.) Look carefully at your httpd.conf and vhosts.conf; factor out the common chunks, make tiny conf files for the small bits that differ by the two apaches (eg the listen port and perl path stuff), and and use includes on these various files to build up the final production.conf and dev.conf files. Believe me, you don't want to try and keep two sets of conf files in sync -- factor out the commonalities and you'll save time over the long run not having to chase down mysterious conf-related bugs.

UPDATE: Another idea: consider moving dev to its own hardware. (Better, as then bad crashes or slowdowns don't harm production.) The dev machine can be very lightweight usually -- a semi-discarded whitebox a few years old running gentoo could very well be powerful enough for dev work and testing. So what if it can't handle load, or takes an extra second to respond -- its for development. With distinct hardware, you can use exactly the same conf files, directory structures, etc on dev and production, making change management, updates, and rollback much easier.

In reply to Re: different versions of same Perl module in different Apache vhosts by water
in thread different versions of same Perl module in different Apache vhosts by agaffney

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.