[Catalyst] Team development and module management

[John Napiorkowski]

>________________________________
> From: Bill Moseley <moseley at hank.org>
>To: The elegant MVC web framework <catalyst at lists.scsys.co.uk> 
>Sent: Monday, December 5, 2011 10:41 AM
>Subject: [Catalyst] Team development and module management
> 
>
>We are slowly replacing a large legacy monolithic application with a (somewhat monolithic) Catalyst app.  There's about a dozen or so developers working mostly on three development boxes.   Much of the code is placed into standard (CPAN-style) modules.  Everything is under revision control (subversion).
>
>
>If you are in a similar work environment how to you manage your internal modules?  Do your developers use something like local::lib or perlbrew to manage their own environments?  Do you run a local CPAN mirror and inject your own in-house modules (so that app dependencies can be installed automatically)?  If so, how and when do modules under revision control end up packaged and how do developers manage module dependencies?
>
>

I have used Perlbrew and local::lib (and my local::lib wrapper, https://metacpan.org/module/App::local::lib::helper) for developers, along with MySQL sandbox ( https://metacpan.org/module/MySQL::Sandbox) for setting up local databases.

Generally my applications never got so big that I needed to have the application in separate distributions, although it seems that having a local cpan mirror and using an injection tool is a pretty accepted approach.

I also use DBIx::Class::Fixtures and DBIx::Class::DeploymentHandler to round out my toolchain, and of course there is Module::Install for managing makefiles.

John

>
>-- 
>Bill Moseley
>moseley at hank.org
>
>_______________________________________________
>List: Catalyst at lists.scsys.co.uk
>Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
>Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
>Dev site: http://dev.catalyst.perl.org/
>
>
>