Hi Gavin, On 19/02/2013, at 3:41 AM, Gavin Eadie <ga...@umich.edu> wrote:
> I've done two WebObjects installs to EC2 using two descriptions from > http://wiki.wocommunity.org, and I've spent time poking around in the > results, and I like to "fix" some things. I'd prefer to work with the > originators of the work in question, but not burden them if they don't want > it. Mainly I don't want to step on work in progress. The page here: http://wiki.wocommunity.org/display/documentation/Deploying+on+Amazon+EC2 was originally written by Simon McLean, formalising and expanding on some scripts and descriptions of work he had posted to the list prior to that. You can see all of the contributors here: http://wiki.wocommunity.org/pages/viewpreviousversions.action?pageId=1049042 I don't think it's a work in progress—edits to that page peaked around 2010-11, and have died off since. For what it's worth, we've been using basically what's described on that page (modified for our own purposes) to build all-in-one application servers from a vanilla Amazon Linux base for a couple of years now, and it works very well for us. > I have two goals: first, to bring the disparate parts of the description of > this process together in one place, eliminating, for example one version > working in "/opt/WOApplications" and the other in > "/opt/Local/Library/WebObjects/...", and second, to make it all more > explicitly instructive ("cook book"). I'm a fan of simplifying, and if there are two pages with two approaches, I think merging them, or at least making it really clear on each of them that the other exists, is a great idea. One difficulty, though, is that dozens of pretty arbitrary decisions go into making something like an application server, and you've just hit on one of them—personally I prefer the simpler /opt/WOApplications directory (completely arbitrary, invented by Simon), yet Pascal prefers the longer /opt/Local/Library/WebObjects for historical reasons. How do you decide? Rhetorical question—no need to answer. But I'm sure you see what I mean. I imagine a lot of the differences between any two approaches would be pretty arbitrary. > Drop me a line if you're a stake-holder, and I'll share. Has this group > adopted a way for side-groups to do thing like this? Is it done in the > "open" or do we suddenly reveal work in a dozen major changes to the wiki?! > Is it hooked to github, where debate is offered? As Pascal mentioned, the mailing list is the main discussion forum. Personally, I think the Wiki should be very collaborative, and there shouldn't be a great need for asking permission to make edits and changes—everything can be reverted anyway. So go for it. Can I ask just one thing: can you leave the note about WOlastic being a dead project somewhere, please? People still stumble across WOlastic from time to time and should know there's no support for it. -- Paul Hoadley http://logicsquad.net/ _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-deploy mailing list (Webobjects-deploy@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-deploy/archive%40mail-archive.com This email sent to arch...@mail-archive.com
