• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Any interest in a Amazon AMI for Wonder?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Any interest in a Amazon AMI for Wonder?


  • Subject: Re: Any interest in a Amazon AMI for Wonder?
  • From: Pascal Robert <email@hidden>
  • Date: Thu, 10 Jan 2013 19:42:17 -0500

Le 2013-01-10 à 19:03, Paul Hoadley <email@hidden> a écrit :

> Hi Pascal,
>
> On 11/01/2013, at 1:40 AM, Pascal Robert <email@hidden> wrote:
>
>> I was wondering if we should build a public AMI (template) on Amazon EC2 that would contains:
>>
>> - CentOS 6.x
>> - The Yum repository for wotaskd/Monitor/the adaptor
>> - RPMForge Yum repository (useful to install software not available from the main CentOS repo)
>> - Postgresql's Yum repository
>> - Jenkins's Yum repository
>
> I would suggest that you don't invest the time doing this, and here's why.  Freezing an AMI like this involves a load of arbitrary decisions (e.g., Why CentOS instead of Amazon Linux?  Why PostgreSQL instead of MySQL?).

That's why I'm adding the Yum repository, but not actually installing PostgreSQL.

>  At each decision, you're carving off a segment of potential users from a base that must already be incredibly small.  Say there's still some interest left, though—who is going to keep this current?  When a security vulnerability is patched in CentOS, are you going to re-roll this?

From my point of view, everyone should take care of security updates. Like you said, keeping the AMI up to date for everyone update would be a mess. The AMI should only be updated for major SSH or Apache, or when CentOS goes from 6.3 to 6.4 or any major update like this.

>  (All these questions are rhetorical, by the way!)  The most likely scenario is that in 18 months we've got a repeat of WOlastic on our hands—when that went stale, it took time and effort to kill off, and I haven't checked lately but I think the AMI itself is _still_ available, though the website is dead.

If we do it, it will be bonded to WOCommunity, I don't want something bonded to a business that might go away.

But anyway, the goal is to make it easier to deploy apps. At least with the Yum repository of WOCommunity, it will be much easier.

> Having said all that, if I haven't discouraged you and you're really keen, I can certainly help you do it.  :-)
>
>
> --
> Paul Hoadley
> http://logicsquad.net/
>
>


 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden


References: 
 >Any interest in a Amazon AMI for Wonder? (From: Pascal Robert <email@hidden>)
 >Re: Any interest in a Amazon AMI for Wonder? (From: Paul Hoadley <email@hidden>)

  • Prev by Date: Re: Any interest in a Amazon AMI for Wonder?
  • Next by Date: has anyone seen this weirdness in JasperReports?
  • Previous by thread: Re: Any interest in a Amazon AMI for Wonder?
  • Next by thread: Re: Any interest in a Amazon AMI for Wonder?
  • Index(es):
    • Date
    • Thread