[Catalyst] Re: Debian recommendation

Mesdaq, Ali amesdaq at websense.com
Wed Oct 28 18:09:06 GMT 2009

I agree. You will only really feel the pain once there are several servers (or several people managing servers)  not counting a dev server. Plus it also deals with scenarios where your software is built using some version of a perl module and your next release of the software is using the newer version of the module with major changes and not much support for backward compatibility. In this case you could be facing issues during deployment if you have several machines that needed to be manually updated or even worse if you automatically update perl modules on production machines then you could be blowing up your app without even changing a line of code. With all that being said I don’t package all my modules because most of my catalyst apps would be deployed on one server and mostly use private perl libraries developed inhouse so it just doesn’t make sense for me but if I had to deploy to several servers and needed to maintain 99.9999% SLA I would spend the time on it. 

Too bad there isn't an cross platform painless elegant solution to this.

Sr. Security Researcher
Websense Security Labs

-----Original Message-----
From: John Lee [mailto:jlee+catalyst at pangeamedia.com] 
Sent: Wednesday, October 28, 2009 10:47 AM
To: The elegant MVC web framework
Subject: Re: [Catalyst] Re: Debian recommendation

Alexander Hartmaier wrote:
> Is building a package for every perl module (not only cpan, private too)
> really of help and not just a waste of time?

I think it's a help once you exceed about twenty servers or so.  YMMV

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/

 Protected by Websense Hosted Email Security -- www.websense.com 

More information about the Catalyst mailing list