flacky Jones's List: Devise

• The @devise_for@ method has a lot of optional parameters to make things easier. If you just want to remove the "users" namespace before all the routes and rename "sign_in", "sign_out" to "login", "logout". Try this way
• devise_for :users, :path => '', :path_names => {:sign_in => 'login', :sign_out => 'logout'}

• The Devise Wiki has lots of additional information about Devise including many "how-to" articles and answers to the most frequently asked questions
• After you install Devise and add it to your Gemfile, you need to run the generator:
• rails generate devise:install
• The generator will install an initializer which describes ALL Devise's configuration options and you MUST take a look at it
• rails generate devise MODEL
• This generator also configures your config/routes.rb file to point to the Devise controller.
• Next, you need to set up the default url options for the Devise mailer in each environment. Here is a possible configuration for config/environments/development.rb:
• config.action_mailer.default_url_options = { host: 'localhost:3000' }
• To set up a controller with user authentication, just add this before_filter:
• before_filter :authenticate_user!
• After signing in a user, confirming the account or updating the password, Devise will look for a scoped root path to redirect. Example: For a :user resource, it will use user_root_path if it exists, otherwise default root_path will be used. This means that you need to set the root inside your routes
• After signing in a user, confirming the account or updating the password, Devise will look for a scoped root path to redirect.
• You can also override after_sign_in_path_for and after_sign_out_path_for to customize your redirect hooks.
• Notice that if your Devise model is called Member instead of User, for example, then the helpers available are:
• before_filter :authenticate_member!  member_signed_in?  current_member  member_session
• The Devise method in your models also accepts some options
• There are just three actions in Devise that allows any set of parameters to be passed down to the model, therefore requiring sanitization
• sign_in
• sign_up
• account_update
• In case you want to permit additional parameters (the lazy way™) you can do with a simple before filter in your ApplicationController
• If you have multiple Devise models, you may want to set up different parameter sanitizer per model. In this case, we recommend inheriting from Devise::ParameterSanitizer and add your own logic
• Since Devise is an engine, all its views are packaged inside the gem.
• you just need to invoke the following generator, and it will copy all views to your application:
• rails generate devise:views
• If you have more than one Devise model in your application (such as User and Admin), you will notice that Devise uses the same views for all models. Fortunately, Devise offers an easy way to customize views.
• All you need to do is set config.scoped_views = true inside the config/initializers/devise.rb file.
• You can also use the generator to generate scoped views:
• rails generate devise:views users

27 more annotations...