Re: New installation fail?
Re: New installation fail?
- Subject: Re: New installation fail?
- From: Paul Yu via Webobjects-dev <email@hidden>
- Date: Tue, 1 Sep 2020 21:14:14 -0400
For Whatever its worth, we on the treasure boat side have switched to
Mod-proxy. We have updated TBMonitor and TBTaskd. I just recently built a
CentOS7 server from scratch and it works great.
Paul
> On Sep 1, 2020, at 8:34 PM, Paul Hoadley via Webobjects-dev
> <email@hidden> wrote:
>
> Hey Jesse,
>
> On 2 Sep 2020, at 01:15, Jesse Tayler via Webobjects-dev
> <email@hidden <mailto:email@hidden>>
> wrote:
>
>> I'm launching a new EC2 Instance and just installing from scratch and I
>> found my way to this page
>>
>> https://wiki.wocommunity.org/display/documentation/Installing+a+deployment+environment+on+RedHat,+CentOS+or+Amazon+Linux
>>
>> <https://wiki.wocommunity.org/display/documentation/Installing+a+deployment+environment+on+RedHat,+CentOS+or+Amazon+Linux>
>>
>> These WO installs all have bad links or dead services?
>
> Seems like there's a lot of bit rot going on.
>
> Rest assured that it's still quite possible (and fairly easy) to set up a
> fresh WebObjects appserver from scratch on EC2. We use Amazon Linux 2—I can't
> vouch for CentOS or RedHat, though there shouldn't be anything that prevents
> it if you're wedded to one of those.
>
> What we use is a heavily customised version of the script posted by Simon
> McLean, possibly as long ago as 2010. I'm digging around in my local list
> archive: I can't see whether the script itself was ever posted, or whether it
> was just a link to an S3 bucket that seems to no longer exist
> (http://webobjects.s3.amazonaws.com/wo-install.sh
> <http://webobjects.s3.amazonaws.com/wo-install.sh>).
>
> I might be able to find the original somewhere, perhaps I can dig around in
> our repo. Meanwhile, the basic outline is very straightforward:
>
> 1. Download JavaMonitor and wotaskd as GZIP bundles from somewhere, e.g.
> wocommunity.org <http://wocommunity.org/>.
> 2. Download mod_WebObjects.so from somewhere—it's very easy to build your own
> binary on an EC2 instance and then you can just stash that somewhere.
> 3. Install Apache with yum.
> 4. Make the usual Apache config modifications for WebObjects.
> 5. Start Apache.
> 6. Unpack the GZIP bundles you downloaded at 1.
> 7. Start JavaMonitor and wotaskd.
>
> Obviously there's a lot of hand-waving going on there. But the takeaway is
> that you don't need to rely on ancient package versions of JavaMonitor and
> wotaskd—you can just pull them from the WOCommunity Jenkins. The rest of it
> is just scripting up the stuff you'd normally do to get them running on any
> Unix.
>
> Let me know if you need more help.
>
>
> --
> Paul Hoadley
> https://logicsquad.net/ <https://logicsquad.net/>
> https://www.linkedin.com/company/logic-squad/
>
> _______________________________________________
> 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
_______________________________________________
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