Yeah... well lighttpd as the balancer is crappy anyway. It just doesn't
perform well cos there are serious bugs in the proxy system. Apache +
mod_proxy_balancer is the way to go.
On 2/8/07, Marlon Moyer [EMAIL PROTECTED] wrote:
Hey Brian,
I must say that I definitely gleaned a lot of knowledge from your site. I
ended up going with an Apache front to several mongrel processes. This
really is an easy way to deploy. Luckily our last asp app is on it's way
out and I think I'll be able to replace IIS with Apache. I just need to
figure out how to do ssl client certs with it now.
I had first tried to use Lighttpd as the balancer with your instructions,
but I guess they've changed up the syntax of the configuration file.
I also found some additional information here:
http://brainspl.at/articles/2006/06/12/apache2-2-vhost-template-for-mongrel-clusters
On 2/8/07, Brian Hogan [EMAIL PROTECTED] wrote:
I'll plug my stuff again
http://www.napcs.com/howto/rails/deploy/index.html
And there's a book coming out that will cover this topic shortly.
On 2/6/07, Aníbal Rojas [EMAIL PROTECTED] wrote:
I have run Apache on W2K, it is really easy to install, and stable.
Its configuration is the same than linux so it should not be a
problem. Putting IIS behind is a very good idea.
--
Aníbal Rojas
http://www.rubycorner.com
http://www.hasmanydevelopers.com
On Feb 6, 10:00 am, Robby Russell [EMAIL PROTECTED]
wrote:
Marlon Moyer wrote:
yes. Aside from ColdFusion and the new RoR apps that I'm
creating,
we're a 100% microsoft shop. Is it possible to run both IIS and
Apache
on the same win32 server? I've never tried that, but as long as
it
wouldn't interfere with the normal IIS operation, I think I could
get
that done.
As for the reverse proxy, that would only hit 1 mongrel process
right?
Apache (2.2) has a proxy balancer, so you could proxy several
mongrel
instances.
Here is a blog post that I just found from a quick google search.
* http://rubyurl.com/z1M
You'll want to look at these sections.
Proxy balancer://mongrel_cluster
BalancerMemberhttp://127.0.0.1:8000
BalancerMemberhttp://127.0.0.1:8001
BalancerMemberhttp://127.0.0.1:8002
/Proxy
and where it's using rewrite to talk to the balancer.
Putting Apache on port 80 and hiding IIS behind it might be a good
solution for many of your hosting needs in your all-windows
environment.
Good luck!
Robby
--
Robby Russellhttp://www.robbyonrails.com/http://www.planetargon.com/
--
Tradin' my time for the pay I get,
Livin' on money that I ain't made yet,
Gotta keep going, gotta find my way,
But I'll live for the end of the day.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Deploying Rails group.
To post to this group, send email to rubyonrails-deployment@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/rubyonrails-deployment?hl=en
-~--~~~~--~~--~--~---