There are many factors that will effect your ideal development environment. Such as:

• Number of developers
• Turn over rate
• Expansion rate
• Typical developer comfort level working with their own copy of mod_perl/Apache
• Testing methods
• Whether mod_perl is needed for those testing methods
• How each developer interacts with the source
• How your code is broken up
• Network latency
• Network stability

If you want to operate in a single mod_perl server environment I recommend you implement and promote thorough unit testing and a human gatekeeper that controls/logs all the updates to the main server in addition to CVS or other revision control systems.

UPDATE Add two items to the list. When I was working with development teams that were on less then reliable networks it became more critical for each development team segment to have their own apache/mod_perl to test on.

---

---

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.