One of the main issues that drove us to run private instances
was the simple goal of allowing
each developer to continue working even if an individual
developer introduced a compile error into their local
codebase. If a module used by the majority of the site
was being worked on, and a syntax, compile, or run-time error
(like calling a typo'd method name) was introduced, it
basicly disabled the other developers.
We re-organized the source code into a hierarchical directory
structure (like you would see in lib/perl5/*) based on package
names. We then just added the source directory to the
@INC used by mod_perl. Each developer used their own
working copy of the CVS archive, something like
$HOME/projects/webSite/lib. The document root for the
web site, as well as the Perl lib path were both under
the same project in CVS.
This also simplified the release process for us, which
basicly ended up being a cvs update on the QA, and then
ultimately production servers.
Kyle
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.