Hi list, This is my first post here, so Hello World! ;-) By default, `rails server` starts webrick on a new rails 3 project. If you include Thin in the gemfile, you can run `rails s thin`to use thin instead. Same works with mongrel. Unfortunately, this does not work with unicorn, since it seems that Rack does not provide a handler for Unicorn by default (as it does for Thin and Mongrel). I know I can run `unicorn` in my app root to achieve the same, but it''d be nice to stick with rails commands and have `rails s unicorn` Can you tell me if such a handler already exists ? ++ Ju
Julien Palmas <julien.palmas at gmail.com> wrote:> Hi list, > > This is my first post here, so Hello World! ;-)Hello Julien :>> By default, `rails server` starts webrick on a new rails 3 project. > If you include Thin in the gemfile, you can run `rails s thin`to use > thin instead. > Same works with mongrel. > > Unfortunately, this does not work with unicorn, since it seems that > Rack does not provide a handler for Unicorn by default (as it does for > Thin and Mongrel). > > I know I can run `unicorn` in my app root to achieve the same, but > it''d be nice to stick with rails commands and have `rails s unicorn` > > Can you tell me if such a handler already exists ?No it does not. Unicorn provides configuration options and signal handler interfaces that Thin and Mongrel do not. Trying to tie them to the same interface would just cripple Unicorn users attempting to use the generic interface and make it more confusing and difficult to support for everyone (Rack/Rails/Unicorn developers). There was a similar discussion here back in 2009: http://thread.gmane.org/gmane.comp.lang.ruby.unicorn.general/130/focus=130 -- Eric Wong