I use Pinto to maintain a per-project repository of dependencies (which is tracked under svn) and install from there into a local::lib.
Deployment is two steps - building the repos in a staging area (via Makefile.PL and cpanm) and then rsyncing the staging code to the production location. Works well where there is a single server per deployment. I previously used Carton but found that Pinto manages dependencies better and has been generally easier to use. On Thu, May 14, 2015 at 7:08 AM, Robert Brown <r...@intelcompute.com> wrote: > One of my previous employers deployed with RPMs. > > And I never understood why. > > It's a good question for the community here, what's your deployment > strategy, and why is it so? > > What would you change if you're not the decision -maker. > > > > > > On 13/05/15 21:58, James Leu wrote: > > Just to add to Robert's idea. > > We use perlbrew and Carton for our catalyst environments > We deploy via RPMs, but each RPM contains a perlprew environment > and a local lib dir managed by Carton. > > On Wed, May 13, 2015 at 06:26:40PM +0100, Robert Brown wrote: > > Not to answer your actual question, but... > > Have you also thought using Perlbrew http://perlbrew.pl > > As regular user, you can install any version of Perl locally (to > your home dir), plus all the modules via cpanm, and keep > everything self-contained for a particular user. > > It's made our deployments a breeze, rather than dealing with the > system-wide perl, etc. > > (There's also local::lib tho I've not delved into that myself). > > Hope it helps a little. > > Rob > > > On 13/05/15 18:16, Duncan Garland wrote: > > Hi, > > I've just spun up a Rackspace server with Ubuntu 14.04 and > tried to install Catalyst from CPAN. > > If the print out means what it seems to mean, then Catalyst > will no longer install cleanly from CPAN on any version prior > to 5.20. > > It's saying that there is a dependency on Tie::StdHash and > that Tie::StdHash won't install without force because the > latest version of the module is part of perl-5.20.2. > > It won't effect me because I'll just force it or download an > older version of the module. > > All the same, it seems a bit poor. > > Is it deliberate? > > Regards > > Duncan > > > > The information contained in this message is for the intended > addressee only and may contain confidential and/or privileged > information. If you are not the intended addressee, please > delete this message and notify the sender; do not copy or > distribute this message or disclose its contents to anyone. > Any views or opinions expressed in this message are those of > the author and do not necessarily represent those of > Motortrak Limited or of any of its associated companies. No > reliance may be placed on this message without written > confirmation from an authorised representative of the > company. > > Registered in England 3098391 V.A.T. Registered No. 667463890 > > > _______________________________________________ > List: Catalyst@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/ > > > > _______________________________________________ > List: Catalyst@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/ > >
_______________________________________________ List: Catalyst@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/