Lighttpd

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Lighttpd

fletcher sandbeck-2
I thought this might be of interest.  We've been experimenting with a few different load balancing schemes and most recently are trying out using a couple rack mounted Mac Mini computers with Lighttpd as front-ends.  We have Lasso running on a separate Xserve so the Minis can just pump out HTML pages and images without distraction.  We're using Unison to sync the web roots on the different machines.

The cool thing is that Lighttpd can seamlessly proxy certain extensions to the Xserve.  We send .lasso, .lassoapp, and even some venerable .ldml pages to the Lasso machine using this configuration option.

proxy.server = (
  ".lasso" => (("host" => "xxx.xxx.xxx.xxx", "port" => 80)),
  ".lassoapp" => (("host" => "xxx.xxx.xxx.xxx", "port" => 80)),
  ".ldml" => (("host" => "xxx.xxx.xxx.xxx", "port" => 80))
)

Lighttpd has a good FastCGI implementation, but I haven't had a chance to see how that plays with Lasso 9 yet.  Hopefully a very similar setup can be used as a front-end to a Lasso 9 instance either on the same machine or remote again.

[fletcher]

#############################################################
This message is sent to you because you are subscribed to
  the mailing list Lasso
[hidden email]
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

Re: Lighttpd

John May-2
On 10/25/11 11:55 PM, Fletcher Sandbeck wrote:

> I thought this might be of interest.  We've been experimenting with a
> few different load balancing schemes and most recently are trying out
> using a couple rack mounted Mac Mini computers with Lighttpd as
> front-ends.  We have Lasso running on a separate Xserve so the Minis
> can just pump out HTML pages and images without distraction.  We're
> using Unison to sync the web roots on the different machines.
>
> The cool thing is that Lighttpd can seamlessly proxy certain
> extensions to the Xserve.  We send .lasso, .lassoapp, and even some
> venerable .ldml pages to the Lasso machine using this configuration
> option.
>
> proxy.server = ( ".lasso" =>  (("host" =>  "xxx.xxx.xxx.xxx", "port"
> =>  80)), ".lassoapp" =>  (("host" =>  "xxx.xxx.xxx.xxx", "port" =>
> 80)), ".ldml" =>  (("host" =>  "xxx.xxx.xxx.xxx", "port" =>  80)) )
>
> Lighttpd has a good FastCGI implementation, but I haven't had a
> chance to see how that plays with Lasso 9 yet.  Hopefully a very
> similar setup can be used as a front-end to a Lasso 9 instance either
> on the same machine or remote again.
>
> [fletcher]
>


FYI, Apache can do this too.  See the "scenario - proxy content based on
file extension" here:

http://www.developerfeed.com/apache/tutorial/how-proxy-static-content-apache-server

        - John

--

-------------------------------------------------------------------
John May : President                   http://www.pointinspace.com/
Point In Space Internet Solutions         800.664.8610 919.338.8198

         Professional FileMaker Pro, MySQL, PHP & Lasso Hosting
           on shared, virtual and hardware dedicated servers

#############################################################
This message is sent to you because you are subscribed to
  the mailing list Lasso
[hidden email]
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

Re: Lighttpd

Brad Lindsay-2
In reply to this post by fletcher sandbeck-2
On Oct 25, 2011, at 11:55 PM, Fletcher Sandbeck wrote:
> Lighttpd has a good FastCGI implementation, but I haven't had a chance to see how that plays with Lasso 9 yet.

For what it's worth, I successfully got Lasso 9 up and running with nginx. I haven't tried 9.1 and instance manager with it yet.


Brad
#############################################################
This message is sent to you because you are subscribed to
  the mailing list Lasso
[hidden email]
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>