> On Jan 14, 2019, at 12:42 PM, fugee ohu <fugee...@gmail.com> wrote: > > > > On Monday, January 14, 2019 at 10:32:23 AM UTC-5, Phil wrote: > > >> On Jan 14, 2019, at 5:35 AM, fugee ohu <fuge...@gmail.com <>> wrote: >> >> >> >> On Sunday, January 13, 2019 at 4:46:52 PM UTC-5, Walter Lee Davis wrote: >> >> >> On Jan 13, 2019, at 12:38 PM, fugee ohu <fuge...@gmail.com <>> wrote: >> >>> What do I need it for besides being able to restart apps >>> >> Passenger is necessary to translate the incoming http request into a >> connection to your Rails app. >> >> Even I f you are just developing locally, you will run `rails s` in a >> console, and that will start a server, usually Puma these days, but you >> could also run Unicorn or even Webrick if you’re feeling nostalgic. >> >> By itself, Rails is not going to respond to http. >> >> Passenger and Unicorn are both production grade http adapters, they can deal >> with things like slow clients or excessive traffic. Webrick (to give a >> ridiculous counter-example) is single-threaded and will just die under >> anything more than development click testing load. >> >> Any of these application servers will want to be fronted by Apache or NGINX >> to handle static assets and general proxy server duties if you anticipate >> any sort of real load. My usual production deployment is Apache with the >> mod_passenger plugin. For really large sites, I will put multiple instances >> of that stack behind a load balancer, with all instances pointing to the >> same database server. >> >> Walter >> >> Rails works with nginx without passenger no? > > Nginx or Apache handle the web connections. Rails is the app. You need some > 'glue' between the two. What something like Passenger does is manages the > Rails processes and keeps connections with Nginx/Apache efficient and uptime > at its most. > > > Phil > > > I thought rails and nginx will work together without Passenger >
You need something to glue Rails and the web service together. (I'd advise against FastCGI, like we did in the Olde Days™ ;') If you are going to use puma (or something) and proxy through nginx or apache, I don't know what the point is(?). Every deployment can be a bit (or a lot) different in needs, though. Passenger is just a plug-in for nginx/apache to manage your rails app pool. I don't understand your attachment to nginx and your aversion to passenger? (I'm not a passenger shrill, just confused what your constraints are.) I think Walter did a good job explaining things, btw. Good luck! Phil -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscr...@googlegroups.com. To post to this group, send email to rubyonrails-talk@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/DEC86A5E-CB8D-4E8D-B562-EA0078F430B6%40gmail.com. For more options, visit https://groups.google.com/d/optout.
