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.

1. Separate the module versions in your repository, paths, branches, however your repo is set-up.
2. Use jails, chroots, containers, VMs, etc, to isolate the deployments.
3. 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 ;)

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&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.