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
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
