I''m trying to understand how the multiple web servers interact w/one another in a rails deployment. If I''ve got thin or mongrel or what have you serving my app, what''s apache doing for me? What can I read to clear this up for me? Thanks! -Roy --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
On Wed, 2008-04-23 at 20:31 -0700, Roy Pardee wrote:> I''m trying to understand how the multiple web servers interact w/one > another in a rails deployment. If I''ve got thin or mongrel or what > have you serving my app, what''s apache doing for me? What can I read > to clear this up for me?---- typically rails is a single threaded process. You can have multiple ''mongrels'' to serve more than 1 thread at the same time in case one thread is tied up. Apache then is used as a proxy to the available mongrels, plus apache can/will cache fixed assets (javascripts/stylesheets) and generally make things fast. Lastly, you tend to run rails in user space and users don''t/shouldn''t have access to port 80 (http) and thus the proxy gets the stuff from high numbered user space tcp ports. Craig --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
Ah--okay then. Thanks! On Apr 23, 8:41 pm, Craig White <craigwh...-BQ75lA0ptkhBDgjK7y7TUQ@public.gmane.org> wrote:> On Wed, 2008-04-23 at 20:31 -0700, Roy Pardee wrote: > > I''m trying to understand how themultipleweb servers interact w/one > > another in a rails deployment. If I''ve got thin or mongrel or what > > have you serving my app, what''s apache doing for me? What can I read > > to clear this up for me? > > ---- > typically rails is a single threaded process. > > You can havemultiple''mongrels'' to serve more than 1 thread at the same > time in case one thread is tied up. > > Apache then is used as a proxy to the available mongrels, plus apache > can/will cache fixed assets (javascripts/stylesheets) and generally make > things fast. > > Lastly, you tend to run rails in user space and users don''t/shouldn''t > have access to port 80 (http) and thus the proxy gets the stuff from > high numbered user space tcp ports. > > Craig--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---