From 61e85a578e93c724443f998ed3d4fadd626d03a4 Mon Sep 17 00:00:00 2001 From: Sammy Larbi Date: Thu, 23 Feb 2012 17:37:13 -0600 Subject: [PATCH] Include note about restarting the rails app if it's already running, because the last 2 apps I used Devise with, I could not figure out why I was getting very strange errors, and finally today I figured out it was due to the fact that it needed to reload. --- README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/README.md b/README.md index 29e1a24e..3f359735 100644 --- a/README.md +++ b/README.md @@ -109,6 +109,8 @@ rails generate devise MODEL Replace MODEL by the class name used for the applications users, it's frequently 'User' but could also be 'Admin'. This will create a model (if one does not exist) and configure it with default Devise modules. Next, you'll usually run "rake db:migrate" as the generator will have created a migration file (if your ORM supports them). This generator also configures your config/routes.rb file to point to Devise controller. +Note that you should re-start your app here if you've already started it. Otherwise you'll run into strange errors like users being unable to login and the route helpers being undefined. + ### Controller filters and helpers Devise will create some helpers to use inside your controllers and views. To set up a controller with user authentication, just add this before_filter: