Why does running one apache/mod_perl server per developer seem like overkill? Trying to sort out the issues involved with running all the modules under one server, particularly multiple @INC paths required for different module versions, is extremely frustrating. And the developers will soon be at each other's throats since they'll have to restart the server all the time, at different times. Since you're in development you can keep the number of servers run per developer very low (2-3) so you shouldn't have resource issues.

It might also be useful (depending on who your users are) to have a single set of lightweight Apache + mod_proxy servers sitting in front of the development servers. Then you can do some fun tricks with mod_rewrite so that a request for http://dev.myco.com/lachoy/ gets proxied (or even just redirected) back to my server running at whatever port is allocated to me. The mod_perl guide has oodles of info on this sort of setup. (A nice side-effect of this is that ordinary users can stop/restart servers running on port > 1024 as often as they like.)

Chris
M-x auto-bs-mode

In reply to Re: Team development on mod_perl + apache by lachoy
in thread Team development on mod_perl + apache by d_i_r_t_y

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.