#3864 "rails server" doesn't start mongrel by default - Ruby on Rails

Type	To find
responsible:me	tickets assigned to you
tagged:"@high"	tickets tagged @high
milestone:next	tickets in the upcoming milestone
state:invalid	tickets with the state invalid
created:"last week"	tickets created last week
sort:number, importance, updated	tickets sorted by #, importance or updated
Combine keywords for powerful searching.
Use advanced searching »

This project is archived and is in readonly mode.

#3864 ✓resolved

"rails server" doesn't start mongrel by default

Reported by Torsten Maul | February 5th, 2010 @ 03:50 PM | in 3.0.2

My environment: Windows XP, Ruby 1.8.7, Rails 3.0.0.beta, Mongrel gem installed

When issueing the command

rails server

in my application path, WEBrick is started, instead of Mongrel. From looking in the documentation, there seems to be no option for setting the server. I tried with

rails server mongrel

, but that doesn't work too.

One workaround I've found, is to call

rackup --server mongrel --port 3000

in your application path.

Comments and changes to this ticket

You flagged this item as spam.
Kieran P February 6th, 2010 @ 08:42 AM
- Tag set to “bug, mongrel, regression, server”
+1 Mongrel should be preferred over thin, and then webrick
José Valim February 6th, 2010 @ 10:07 AM
- Milestone cleared.
Prem Sichanugrist (sikachu) February 8th, 2010 @ 07:43 PM
- State changed from “new” to “open”
- Tag changed from “bug, mongrel, regression, server” to “bug, mongrel, patch, regression, server”
- Assigned user set to “José Valim”
The reason why rails server use Webrick over Mongrel was because the way gems area specify in the bundler. If you don't specify it in Gemfile, then rails server, or Rack more specifically, won't be able to use it.

So here, I'm proposing the patch for adding two commented lines suggesting them to put gem 'mongel' in case they want to use Mongrel.

@Kieran P

Right now, the order of server, or handler, is specify by Rack. I don't know how could I patch that. Please see http://github.com/rack/rack/blob/master/lib/rack/handler.rb#L36 for more information.
- 0001-add-gem-mongrel-to-application-template-s-gemfile-to.patch 1 KB
Prem Sichanugrist (sikachu) February 9th, 2010 @ 08:54 AM
It seems like I need to add :group => :development for that Gemfile. Another patch ...
- 0001-add-gem-mongrel-to-application-template-s-gemfile-to.patch 1 KB
You flagged this item as spam.
Craig Buchek February 9th, 2010 @ 05:05 PM
While I'd prefer Mongrel to be used automatically, Prem's patch to add it (commented out) to the Gemfile seems to be a reasonable solution. The only way I can see to make it automatic would be something like this:

gem "mongrel", :group => :development rescue nil

But I don't know if that would work or make any sense.
Prem Sichanugrist (sikachu) February 10th, 2010 @ 01:45 AM
- State changed from “open” to “resolved”
Craig Buchek

No, that won't do any good. If you specify that, Bundler would try to load/install the gem anyway.

However, this patch is stale now by this commit from DHH, so I'll mark it as resolved. Seems like if you want to use Mongrel, uncommenting it from Gemfile would be a way to go.

http://github.com/rails/rails/commit/834a45d8a2ae225b775c51d8ae266a...
Jeremy Kemper October 15th, 2010 @ 11:01 PM
- Milestone set to “3.0.2”
[bulk edit]
You flagged this item as spam.
bingbing March 26th, 2011 @ 02:09 AM
- Tag changed from “bug, mongrel, patch, regression, server” to “server, bug, mongrel, patch, regression”
louis vuitton watches