You may want to take a look at Bugzilla. It is an open source Bug Tracking facility written in Perl which has much of the functionallity you are intersted in (though it deals with bugs).
It defaults to use MySQL but I believe it can use Postgresql as well (though I don't think it is as trivial as a configuration option).
Also, as a side note, the whole O'Reilly Practical ModPerl book is online and a good read, though it covers alot on the administration side.
I have to agree though, I haven't found much on good practices for structuring/organizing/developing large perl projects/systems.
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.