IMO you are solving the wrong problem :) The problem is you have two environments (for now :-)) and you are storing & deploying them together. This can only end in tears when change X for team Y affects team Z and you have no idea why Team Z's production app suddenly exploded when no one touched it.
- Separate the module versions in your repository, paths, branches, however your repo is set-up.
- Use jails, chroots, containers, VMs, etc, to isolate the deployments.
- Only expose the appropriate repository version to each deployment.
Personally I'd just use your OS's package manager for the modules as it makes isolating deploying & upgrading individual systems easier to orchestrate if the environment starts to scale out ... but I also prefer cider to beer so YMMV ;)
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>
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
Want more info? How to link or
or How to display code and escape characters
are good places to start.