Re^3: Application deploymentt

in reply to Re^2: Application deploymentt
in thread Application deploymentt

...raid failure on one of prod servers where we had no backup...

Ok, really? That isn't a problem with CPAN or modules. That is just being cheap and getting burned by it.

...during fresh install one of deps had memory leak in version...

At first glance I thought this was the more legitimate reason to avoid using CPAN but then again, how do you know that any shared library you are upgrading to on a production system isn't going to bring about a similar problem?

Celebrate Intellectual Diversity

Comment on Re^3: Application deploymentt

Replies are listed 'Best First'.
Re^4: Application deploymentt by Anonymous Monk on Feb 07, 2012 at 14:43 UTC
Sure it is not CPAN problem. But I might solve future failures (if any) by having local::lib in git repo. While testing/develpoing, I can see that libX ver.123 got memory leak/bug/etc. So I push to local::lib ver.111 that has no problems. In this way - there is no need to install ver.111 manually on multiple servers. Just pull, everything from git repo, that was tested, and confirmed to work previosly.	[reply]

Replies are listed 'Best First'.

Re^4: Application deploymentt
by Anonymous Monk on Feb 07, 2012 at 14:43 UTC

Sure it is not CPAN problem. But I might solve future failures (if any) by having local::lib in git repo.

While testing/develpoing, I can see that libX ver.123 got memory leak/bug/etc. So I push to local::lib ver.111 that has no problems. In this way - there is no need to install ver.111 manually on multiple servers. Just pull, everything from git repo, that was tested, and confirmed to work previosly.

[reply]

In Section Seekers of Perl Wisdom