Mailing-List: contact modperl-help@perl.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (athena.apache.org: domain of tosh@1200group.com designates
 209.85.214.49 as permitted sender)
Message-ID: <4E197ED7.2060707@1200group.com>
Date: Sun, 10 Jul 2011 12:28:39 +0200
From: Tosh Cooey <tosh@1200group.com>
Organization: Twelve Hundred Group LLC
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US;
 rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: "modperl@perl.apache.org" <modperl@perl.apache.org>
CC: Dave Hodgkinson <davehodg@gmail.com>
Subject: Re: Re: mod_perl EC2 AMI's or other platform providers?
References: <4E12EABD.1050505@1200group.com>
In-Reply-To: <4E12EABD.1050505@1200group.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Mr. Hodgkinson was awesome enough to point out the existence of 
DotCloud: https://docs.dotcloud.com/#perl.html

Looks there like they have a Perl stack available, which is super for 
the world but not so for me since the stack requires you use PSGI which 
is a great approach but since I don't require portability I never went 
that route, oh woe is me...

Anyway, it's good to see there's some good Perl options out there for 
getting rid of my admin(s).

Thanks Dave!

Tosh


On 7/22/64 8:59 PM, Tosh Cooey wrote:
> 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/