There's a note in the build file -- due to WO bug don't use tomcat 8 unless
you replace WOJavaServletAdapter or whatever its called. Use tomcat 7.
On Fri, Mar 6, 2015, 9:09 AM John Huss wrote:
> Here's what I can do now:
>
> https://www.dropbox.com/s/bfgmzkrz6cyw1xe/buid.xml?dl=1
>
> https://ww
Here's what I can do now:
https://www.dropbox.com/s/bfgmzkrz6cyw1xe/buid.xml?dl=1
https://www.dropbox.com/s/56cojqgulc7sezj/Application.java?dl=1
On Thu, Mar 5, 2015 at 2:49 PM Paul Hoadley wrote:
> Hi John,
>
> On 6 Mar 2015, at 2:01 am, John Huss wrote:
>
> Are you doing any of this in pra
Hi John,
On 6 Mar 2015, at 2:01 am, John Huss wrote:
> Are you doing any of this in practice? How do you handle session persistence?
>
> Yes, I have a very high traffic WO app deployed this way -- but it is purely
> web services and javascript, no components. It used EOF originally, but now
Oh, I should say also -- I have a Play 2 app running on beanstalk deployed
inside a docker container also. Play provides built-in support for
building a docker image. However, it is not complicated to do yourself
(with WO for example).
I still have some other WO apps running internally outside o
On Wed, Mar 4, 2015 at 4:01 PM Paul Hoadley wrote:
> Hi John,
>
> On 5 Mar 2015, at 7:13 am, John Huss wrote:
>
> You're missing out big time using the traditional deployment model on
> AWS. If you instead use an deployment model that includes an elastic load
> balancer you get a ton of benefit
On Thu, 05 Mar 2015 08:30:49 +1030
Paul Hoadley wrote:
> Hi John,
>
> On 5 Mar 2015, at 7:13 am, John Huss wrote:
>
> > You're missing out big time using the traditional deployment model
> > on AWS. If you instead use an deployment model that includes an
> > elastic load balancer you get a to
Hi John,
On 5 Mar 2015, at 7:13 am, John Huss wrote:
> You're missing out big time using the traditional deployment model on AWS.
> If you instead use an deployment model that includes an elastic load balancer
> you get a ton of benefits:
>
> 1) it automatically replaces dead instances.
> 2)
My own 2 cents --
You're missing out big time using the traditional deployment model on AWS.
If you instead use an deployment model that includes an elastic load
balancer you get a ton of benefits:
1) it automatically replaces dead instances.
2) it can automatically scale up if needed
3) lots of
This is how we do it too - much safer.
On Feb 28, 2015, at 3:02 PM, Matthew Ness wrote:
> Hi Ray,
>
> We do a lot of deployment to AWS environments (although not Ubuntu,
> still linux). One thing I would recommend here is with this step:
>
>> - change the security group to add the ability to a
Hi Ray,
We do a lot of deployment to AWS environments (although not Ubuntu,
still linux). One thing I would recommend here is with this step:
> - change the security group to add the ability to allow an inbound
> connection to the instance on port 56789.
>
> - ssh into the new instance and the
I am trying to set up some configurations using AWS and, probably,
Docker. In th meantime, I set this up and am going to leave it up and
build on it.
I have reviewed the pages on wocommunity.org about this and I do not
even know where to begin to fix that. Anyway.
- create a new EC2 instance. I
11 matches
Mail list logo
