Skip to content
Browse files

remove Mongrel from debugger docs

  • Loading branch information...
1 parent ebe61bf commit cffae06a4f1b7aac86a7e99cfb244890f837f976 @robzolkos robzolkos committed Oct 15, 2010
Showing with 1 addition and 3 deletions.
  1. +1 −3 railties/guides/source/debugging_rails_applications.textile
View
4 railties/guides/source/debugging_rails_applications.textile
@@ -250,16 +250,14 @@ Make sure you have started your web server with the option +--debugger+:
<shell>
~/PathTo/rails_project$ rails server --debugger
-=> Booting Mongrel (use 'rails server webrick' to force WEBrick)
+=> Booting WEBrick
=> Rails 3.0.0 application starting on http://0.0.0.0:3000
=> Debugger enabled
...
</shell>
TIP: In development mode, you can dynamically +require \'ruby-debug\'+ instead of restarting the server, if it was started without +--debugger+.
-In order to use Rails debugging you'll need to be running either *WEBrick* or *Mongrel*. For the moment, no alternative servers are supported.
-
h4. The Shell
As soon as your application calls the +debugger+ method, the debugger will be started in a debugger shell inside the terminal window where you launched your application server, and you will be placed at ruby-debug's prompt +(rdb:n)+. The _n_ is the thread number. The prompt will also show you the next line of code that is waiting to run.

0 comments on commit cffae06

Please sign in to comment.
Something went wrong with that request. Please try again.