On 4 Jul 2011, at 21:56, Tosh Cooey wrote: > On 7/4/11 7:54 PM, Dave Hodgkinson wrote: >> >> On 4 Jul 2011, at 11:03, Tosh Cooey wrote: >> >>> The only public AMI for EC2 setup with mod_perl I can easily find is an >>> OpenSuse one from 2009. >>> >>> Services like Bitnami are a really nice platform for launching LAMP stacks, >>> unfortunately the P is anything but Perl :( >>> >>> Is there a reason for the lack of plug'n'play mod_perl LAMP cloud service >>> providers? Or are there a ton that I just don't know about? >> >> >> Glad you're happy with perl 5.8.8 and old, possibly buggy CPAN modules. >> > > > I'm not happy, hence the complaining about the AMI from 2009. But I'm glad > you changed the subject from your first one, which is that I should build my > own stack. > > So basically you are saying (and only you, not a community voice) that in > order to be a mod_perl developer one also needs to: > > 1) Build and optimize Apache. > 2) Build and optimize MySql. > 3) Build and optimize Perl+mod_perl. > 4) Build and optimize a Linux server environment. > or > 5) Have enough money to pay for all of the above.
You have no stack. Make one. Better still, get a bunch of people together with the same problem. Dunno where you'd find 'em. I just spent six months helping a company do exactly[0] this and move off a dated RH platform onto a modern, current, Debian, perl 5.14, all new CPAN modules. The developers were unleashed with modern perl and moduels and the admins didn't have to worry about holding together decrepit operating systems with known issues. There's a benefit. It doesn't take that long to build a perl, load it with modules (especially with cpanm), compile an Apache and a mod_perl. As for optimize, I've always found gentoo-safe flags for the arch you're targetting to work pretty well. And the developers got exactly the perl they wanted: fully 64-bit internals. (Having a core committer on the team helped and a few other perl world stalwarts besides). Sorry to have been so blunt about it but you have a problem and have an issue with adressing it. [0] A small part of the six months, there was a lot of other stuff going on too :)
