aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorschneems <richard.schneeman@gmail.com>2012-06-01 16:44:41 +0200
committerschneems <richard.schneeman@gmail.com>2012-06-01 16:46:11 +0200
commite63666398d77fcca46308eff63dce144dd199479 (patch)
tree0640240455adb1f89e577e98988676bbbf7547bf
parentf87820d00acc4a699f2bb405fa33d4f1054ec52d (diff)
downloadrails-e63666398d77fcca46308eff63dce144dd199479.tar.gz
rails-e63666398d77fcca46308eff63dce144dd199479.tar.bz2
rails-e63666398d77fcca46308eff63dce144dd199479.zip
routes are viewable in browser (update guides)
From the Pull Request #6461
-rw-r--r--guides/source/routing.textile4
1 files changed, 2 insertions, 2 deletions
diff --git a/guides/source/routing.textile b/guides/source/routing.textile
index 0773a96c67..6bd08185be 100644
--- a/guides/source/routing.textile
+++ b/guides/source/routing.textile
@@ -859,9 +859,9 @@ h3. Inspecting and Testing Routes
Rails offers facilities for inspecting and testing your routes.
-h4. Seeing Existing Routes with +rake+
+h4. Seeing Existing Routes
-If you want a complete list of all of the available routes in your application, run +rake routes+ command. This will print all of your routes, in the same order that they appear in +routes.rb+. For each route, you'll see:
+If you want a complete list of all of the available routes in your application, visit +http://localhost:3000/rails/info/routes+ in your browser while your server is running in the development environment. If your local server is not running, you can execute the +rake routes+ command in your terminal to produce the same output. This will print all of your routes, in the same order that they appear in +routes.rb+. For each route, you'll see:
* The route name (if any)
* The HTTP verb used (if the route doesn't respond to all verbs)