If you are installing Catalyst over a previous setup, or at least something
where Moose already exists try using the moose-updated helper script to see if
that clears stuff up -jnap
On Thursday, May 14, 2015 4:47 AM, Duncan Garland
duncan.garl...@motortrak.com wrote:
Hi John,
I
Hi John,
It's system Perl. Logged in a root, logged into cpan, typed install
Catalyst.
It's a clean Rackspace server running Ubuntu 14.04. I created it yesterday
afternoon because I wanted to prototype something.
Catalyst installs correctly from the rpms ( apt-get install
libcatalyst-perl,
Hi Duncan,
wow thats a lot of errors... this is system Perl now or a local lib, I got lost
a bit in the thread above.
On Thursday, May 14, 2015 4:47 AM, Duncan Garland
duncan.garl...@motortrak.com wrote:
Hi John,
I didn't save all the terminal output, but here's what I have got
Hi John,
I've been looking at this some more and I'm not sure if the server is set
up correctly.
These problems may not occur on a properly configured server.
I'll let you know when I've got more information.
Regards
Duncan
On Thu, May 14, 2015 at 2:22 PM, John Napiorkowski jjn1...@yahoo.com
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...
As an FYI,
Since I'm on a new project anyway, we've been able to pick up the latest
version of Perl, and a snapshot of those libs and run with it.
Our main product has been going 3 years, with no issues.
Easy to try out a new Perl and/or modules
On 13/05/15 21:58, James Leu wrote:
Just
Excellent idea Robert. I've been doing it this way
for so long, it would be nice to take fresh view at
how others are doing it.
For us RPM add two benifits:
- It allows us to validate that files have not changed from
the originial reployed version.
- I can give our Ops team a RPM and have them
I'd love to see a full install attempt. I was getting tests for Perl down to
5.8.8 before we release so I am not aware of a hard dependency on Tie::StdHash.
However I don't use cpanplus, and I write my own makefile.pl, not the one that
Catalyst::Devel writes. Its possible that something is
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
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.
RPMs work for us at the moment but that's because it's what our sysadmin
likes. In previous jobs I've had a system wide perl compiled into
Maybe I'm benefiting from a platform of only 40 servers, tho I'm not
sure what our limits would be.
For us they're simple (virtual) web servers.
If one plays up, drop it, rebuild, and away we go, I kinda got that from
Yahoo! Don't worry about what went wrong, just rebuild and carry on.
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
Hi,
We don't use perlbrew on production, but I've used it in other areas
without a problem. As far as I know it's very highly regarded.
I've used local::lib successfully for development work ie Temporarily
pointing to some different modules.
I spent quite a lot of time at the beginning of this
! When I ran force install Tie::StdHash it downloaded
perl-5.20.2.tar.gz and started to install it.
I killed that pretty quicky.
There is a serious problem here.
On Wed, May 13, 2015 at 6:26 PM, Robert Brown r...@intelcompute.com wrote:
Not to answer your actual question, but...
Have
Interesting, we don't use local::lib, just perlbrew, both dev and
production, and keep the whole perlbrew dir in svn, works great.
Will let the catalyst devs answer the actual/original question...
On 13/05/15 19:01, Duncan Garland wrote:
Hi,
We don't use perlbrew on production, but I've
15 matches
Mail list logo
