You can have more than one domain per IP address served by different
applications with Nginx up front. You can swap from one instance of an
application to another (semi-seamless upgrades) with Nginx up front. You
can front many different Lift instances (some running on other machines)
with
On Mon, Jan 4, 2010 at 7:25 PM, Alex Black a...@alexblack.ca wrote:
I'm intrigued by the Nginx, could you tell us more about what the
advantages of using Nginx as well as Jetty instead of Jetty?
You can have more than one domain per IP address served by different
applications with Nginx up
I'm not trying to load-balance. Upstream seems to be oriented to load
balancing, which is not the goal. Did I miss something?
Sorry for the late reply - indeed it is for load balancing etc; I was
working on the presumption you might have more than one back-end jetty
- if not then sure, what
On Tue, Nov 11, 2008 at 1:52 PM, Tim Perrett [EMAIL PROTECTED] wrote:
Good to see that your using nginx dave... It's a rocking front end.
One thing, what made you use proxy_pass rather than upstream ?
I'm not trying to load-balance. Upstream seems to be oriented to load
balancing, which is
Good to see that your using nginx dave... It's a rocking front end.
One thing, what made you use proxy_pass rather than upstream ?
Cheers, Tim
Sent from my iPhone
On 11 Nov 2008, at 21:11, Viktor Klang [EMAIL PROTECTED] wrote:
Thanks for the how-to Dave!
Looks splendid :)
On Tue, Nov 11,
Upstream let's you specify a bunch of backend servers, say you had 3
nodes running your app in a cluster, upstream can manage and load
balence the sending of requests to those backends.
I'm on my iPhone right now, so can't copy and paste a link - check out
the code mongers wiki... I'll
