Sorry to be dumb, but where do I tell wotaskd and JavaMonitor to look for the Configuration directory? My deployment just built from Wonder is looking for "/opt/Local/Library/WebObjects/Configuration/" which isn't how I have it set up at present, so I want to point it elsewhere. John
On 18 Feb 2013, at 17:52, Gavin Eadie <ga...@umich.edu> wrote: > On Feb 18, 2013, at 12:30 PM, Pascal Robert <prob...@macti.ca> wrote: > >> >> Le 2013-02-18 à 12:28, Gavin Eadie <ga...@umich.edu> a écrit : >> >>> On Feb 18, 2013, at 12:17 PM, Pascal Robert <prob...@macti.ca> wrote: >>> >>>> Le 2013-02-18 à 12:11, Gavin Eadie <ga...@umich.edu> a écrit : >>>> >>>>> 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. >>>>> >>>>> 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 always use /opt/Local/Library/WebObjects/ + /opt/Library because it was >>>> the Apple default on UNIX (Solaris, Linux, BSD). >>> >>> .. I certainly prefer it to a "top level" use of "/opt/" though I'd happily >>> lose the "Local/Library" folderol. Don't worry, I'll leave that sleeping >>> dog snoring loudly! >> >> But if we change the paths, that means the RPMs have to change (not a big >> thing to do) but we also need to add a script to migrate everything to the >> new location, so apps, Monitor and wotaskd have to be stopped for this. > > .. Understood. My preference is not for a third, new convention. The one > used in the RPMs is OK (modulo my comments in another thread, which I not > pursuing for now). My target is pages like: > > "http://wiki.wocommunity.org/display/documentation/Deploying+on+Amazon+EC2"; > > which are not consistent with your (and my) choice for the RPMs. > >>>>> 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? >>>> >>>> Mailing list is still the primary place for discussions. Or add a page on >>>> the wiki with the changes you want to do, but notify the mailing list or >>>> else almost nobody will see the new page. >>> >>> .. New page and notification seems a good way to go as long as when I'm >>> done it's OK to render the old stuff invisible. >>> >> > > > _______________________________________________ > 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/john%40pollardweb.com > > This email sent to j...@pollardweb.com _______________________________________________ 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
