thin

Ruby process is single thread. When we start a single process using thin server, why are we still able to handle concurrency request? require 'sinatra' require 'thin' set :server, %w[thin] get '/test' do sleep 2 <---- "success" end What is inside thin that can handle concurrency request? If it is due to event-machine framework, the code above is actually a sync code which is not for EM used. Quoting the chapter: "Non blocking IOs/Reactor pattern" in http://merbist.com/2011/02/22/concurrency-in-ruby-explained/ : "this is the approach used by Twisted, EventMachine and Node.js. Ruby developers

I have installed thin and try to do thin start , which end up with this error C:/Ruby192/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require': no such file to load -- C:/Ruby192/lib/ruby/gems/1.9.1/gems/thin-1.2.8-x86-mingw32/lib/1.9/thin_parser (LoadError) from C:/Ruby192/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from C:/Ruby192/lib/ruby/gems/1.9.1/gems/thin-1.2.8-x86-mingw32/lib/thin.rb:48:in `rescue in <top (required)>' from C:/Ruby192/lib/ruby/gems/1.9.1/gems/thin-1.2.8-x86-mingw32/lib/thin.rb:43:in `<top (required)>' from C:/Ruby192/lib/ruby/site

Deploying my first web app. I have been using thin, it's simple and easy. All I need is a config file. But a lot of people use nginx and place a couple thin instance behind that. Why? Why not just use thin alone? And why use nginx rather than placing 3 thin instances behind a single thin instance? Thanks Scalability is the main reason. While Thin can do SSL, serve static files, and handle large responses to slow clients, Nginx is better at all of them for any given CPU and memory footprint. Even better, Nginx can do all that transparently so that the app doesn't have implement anything to

I recently added a subdomain constraint to my Rails routes file constraints(:subdomain => 'new') do devise_for :customers do get "/customers/sign_up" => "registrations#new" post "/customers" => "registrations#create" put "/customers/:id" => "registrations#update" end match '/' => 'roxy#index' namespace :roxy, :path => '/' do resources :customers resources :surveys end end In order to test the subdomain routing constraint locally, I added this line to my hosts file. 127.0.0.1 new.localhost.local Now, I test my app in my browser at the URL new.localhost.local:3000. It takes about 10 - 15 seconds

Question Can you use thin with ActionController::Live to implement Server Side Events (SSE) and long polling? If so, how? Context Although the title is a repeat of How to get Rails 4 ActionController::Live streaming working with Thin and Ruby 2? And how do Thin and Puma scale with live streaming? , the OP muddied the waters by asking two questions, and this question never got answered. A number of other posts suggest you CAN use thin for Server Side Events (sse) if you start it via exec thin start --threaded : Does Heroku support ActionController::Live? and Is puma the ONLY multi-threaded

I want to be able to terminate a Sinatra app from a request, e.g. with the following route: post '/terminate' do Thread.current.kill end Implementing it like this is a bit abrupt. I'd rather the request completed, returned an HTTP OK message, and then Sinatra shut down gracefully. Is there a hook to do this? Edit: My application is a lightweight mock server used for receiving webhook notifications. I will be using multiple servers like this on the same machine (different ports), so need to avoid any global methods of starting/stopping. My requirement is driven by the fact that each server must