Yes thanks for this well I am pretty set with nginx + passenger. Once I spent the week end digging into it I am pretty happy and it is the recommended way to deploy by many so I will trust this setup for now. I like this more than moving parts with reverse proxies and since it will end up to me to manage this I want to keep it simple as time is scarce ;)
On Mon, Apr 2, 2012 at 11:08 AM, Nokan Emiro <uzleep...@gmail.com> wrote: > On fastcgi - fastcgi is not a server in itself - you cannot connect to it >> with a web browser. Like Passenger, it's a way for a server like nginx or >> apache to launch and talk to processes which return webpages directly. >> > > FastCGI IS a server in itself - you can connect to it, but not with a web > browser. It's because it uses a protocol called fastcgi, not http. (The > easiest way to interact with it is to use the cgi-fcgi command from command > line...) It is not necessary to use the webserver to launch the fcgi > processes, they can be configured just to connect to these servers, and you > can run them whatever way you want. (I use simple init scripts for this > purpose, but in a specialized hosting environment you must build a launcher > for them, that handles new uploads, handles broken scripts (those that die > after starting), and this system has to manage with ports associated with > users, like in the case of using thin and reverse proxies.) > > > > _______________________________________________ > Camping-list mailing list > Camping-list@rubyforge.org > http://rubyforge.org/mailman/listinfo/camping-list >
_______________________________________________ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
