Re: mod_perl EC2 AMI's or other platform providers?
On 7/4/11 11:26 PM, Dave Hodgkinson wrote: 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. You seem to have missed the point of my kvetching, which is perhaps a suitable answer anyway. Thank-you. Tosh -- McIntosh Cooey - Twelve Hundred Group LLC - http://www.1200group.com/
Re: mod_perl EC2 AMI's or other platform providers?
On 5 Jul 2011, at 08:53, Tosh Cooey wrote: > On 7/4/11 11:26 PM, Dave Hodgkinson wrote: >> >>> >>> 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. > > > You seem to have missed the point of my kvetching, which is perhaps a > suitable answer anyway. What was the point?
Re: mod_perl EC2 AMI's or other platform providers?
Dave Hodgkinson wrote: On 5 Jul 2011, at 08:53, Tosh Cooey wrote: On 7/4/11 11:26 PM, Dave Hodgkinson wrote: 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. Ah, the beauty of being able to apt-get install libapache2-mod-perl2 You seem to have missed the point of my kvetching, which is perhaps a suitable answer anyway. What was the point? Rather than slinging it out in public, you may want to consider.. There are bound to be different points of view for this kind of issue, from different kinds of users. I see the same on other forums to which I subscribe (Apache, Tomcat). It is like a triangle. In corner A, there are developers who want to have the latest versions of their particular packages of interest and be able to fine-tune their setup for easy development, debugging, bug reporting etc.., but do not care very much if other packages consequently run less well on the same server. In corner B are mere users, who just want the applications to work 24/24, and could not care less about the underlying package versions as long as it does work. And in corner C are sysadmins, who are supposed to manage an ever-increasing number of servers, install something on request of A or B within the next 5 minutes, and then keep all the servers up-to-date OS-wise and many-different-packages-wise over time. Since all of them want to sleep at night and take holidays from time to time, these different positions/requirements are bound to conflict occasionally. Depending on the people involved, the size of the organisations, the budgets at stake etc, these groups may overlap or not and have different weights, so the shape and point of equilibrium of the triangle will be different in each case. And I'm sure that it's a polygon rather than a mere triangle. There certainly isn't one answer which fits all. Personally, I must say that statements like "I just spent six months helping a company do exactly[0] this" make me dream. I must be in the wrong triangle...
Re: mod_perl EC2 AMI's or other platform providers?
On 5 Jul 2011, at 10:53, André Warnier wrote: > Personally, I must say that statements like "I just spent six months helping > a company do exactly[0] this" make me dream. I must be in the wrong > triangle... > It was an interesting dynamic. Ownership of the Apache stack moved to the developers, based on their skillset. It was regarded as part of the application they were developing. I also got to introduce sanity to their Selenium usage but that's another story :)
Re: mod_perl EC2 AMI's or other platform providers?
The point was, and is, that it's unfortunate that mod_perl developers need 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. Those are all roadblocks to development, much like your responses are to this discussion. My life would be a different experience if I could pay for six months of your time whenever I wanted to create a new web application. It would be nice to fire up a mod_perl stack somewhere (say EC2) and then just modify startup.pl and install your required modules and go. The dev world is moving away from requiring system administrators and towards more PaaS'. Tosh On 7/5/11 10:48 AM, Dave Hodgkinson wrote: On 5 Jul 2011, at 08:53, Tosh Cooey wrote: On 7/4/11 11:26 PM, Dave Hodgkinson wrote: 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. You seem to have missed the point of my kvetching, which is perhaps a suitable answer anyway. What was the point? -- McIntosh Cooey - Twelve Hundred Group LLC - http://www.1200group.com/
Re: mod_perl EC2 AMI's or other platform providers?
Le lundi 04 juillet 2011 à 23:00 +0200, Tosh Cooey a écrit : > On 7/4/11 12:33 PM, Dave Hodgkinson wrote: > >> 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? > >> > > > > Because you really should build your own perl, mod_perl and Apache stack. > > > > I fail > to see a benefit in building your own perl, mod_perl and Apache stack. > A plug'n'play Apache/mod_perl stack sounds to me like an oxymoron, specially if you also use a database. If you need that power, you must be able to tune it, maybe not for optimization but certainly for security. I haven't used it myself, but this was mentionned on the list a few days back : http://plackperl.org/ Maybe that's more adapted for your needs? As far as building a stack goes, I agree with André's reply in the other part of this thread : "Ah, the beauty of being able to apt-get install libapache2-mod-perl2" This is what I use: apt-get install libapache2-request-perl libapreq2 libapache-dbi-perl libapache2-mod-perl2 apache2-mpm-prefork apache2-doc apache2-utils #edit /etc/apache2/conf.d/security ServerSignature Off ServerTokens Minimal I have to install a few Perl modules that I use, but all that's left to do is create the virtual hosts files to be up and running. -- Vincent Veyron http://marica.fr/ Logiciel de gestion des sinistres et des contentieux pour le service juridique
