Hi Pascal, On 11/01/2013, at 1:40 AM, Pascal Robert <[email protected]> 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?). 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? (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. 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 protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
