2009-11-03 07:11:36 -05:00
|
|
|
# Use this hook to configure devise mailer, warden hooks and so forth. The first
|
|
|
|
# four configuration values can also be set straight in your models.
|
|
|
|
Devise.setup do |config|
|
2010-06-12 14:56:55 -04:00
|
|
|
# ==> Mailer Configuration
|
2010-01-06 08:31:00 -05:00
|
|
|
# Configure the e-mail address which will be shown in DeviseMailer.
|
|
|
|
config.mailer_sender = "please-change-me@config-initializers-devise.com"
|
|
|
|
|
2010-06-12 14:56:55 -04:00
|
|
|
# Configure the class responsible to send e-mails.
|
|
|
|
# config.mailer = "Devise::Mailer"
|
|
|
|
|
2010-05-16 13:13:20 -04:00
|
|
|
# ==> ORM configuration
|
|
|
|
# Load and configure the ORM. Supports :active_record (default), :mongoid
|
|
|
|
# (bson_ext recommended) and :data_mapper (experimental).
|
|
|
|
require 'devise/orm/<%= options[:orm] %>'
|
|
|
|
|
2010-03-29 10:13:19 -04:00
|
|
|
# ==> Configuration for any authentication mechanism
|
|
|
|
# Configure which keys are used when authenticating an user. By default is
|
|
|
|
# just :email. You can configure it to use [:username, :subdomain], so for
|
|
|
|
# authenticating an user, both parameters are required. Remember that those
|
|
|
|
# parameters are used only when authenticating and not when retrieving from
|
|
|
|
# session. If you need permissions, you should implement that in a before filter.
|
|
|
|
# config.authentication_keys = [ :email ]
|
|
|
|
|
2010-04-01 16:11:59 -04:00
|
|
|
# Tell if authentication through request.params is enabled. True by default.
|
|
|
|
# config.params_authenticatable = true
|
|
|
|
|
|
|
|
# Tell if authentication through HTTP Basic Auth is enabled. True by default.
|
2010-03-29 14:52:34 -04:00
|
|
|
# config.http_authenticatable = true
|
|
|
|
|
2010-03-29 10:13:19 -04:00
|
|
|
# The realm used in Http Basic Authentication
|
|
|
|
# config.http_authentication_realm = "Application"
|
|
|
|
|
|
|
|
# ==> Configuration for :database_authenticatable
|
2010-06-12 08:46:55 -04:00
|
|
|
# For bcrypt, this is the cost for hashing the password and defaults to 10. If
|
|
|
|
# using other encryptors, it sets how many times you want the password re-encrypted.
|
|
|
|
config.stretches = 10
|
2009-11-03 07:11:36 -05:00
|
|
|
|
2010-06-12 08:46:55 -04:00
|
|
|
# Define which will be the encryption algorithm. Devise also supports encryptors
|
|
|
|
# from others authentication tools as :clearance_sha1, :authlogic_sha512 (then
|
|
|
|
# you should set stretches above to 20 for default behavior) and :restful_authentication_sha1
|
2010-01-07 16:37:47 -05:00
|
|
|
# (then you should set stretches to 10, and copy REST_AUTH_SITE_KEY to pepper)
|
2010-06-12 08:46:55 -04:00
|
|
|
config.encryptor = :bcrypt
|
|
|
|
|
|
|
|
# Setup a pepper to generate the encrypted password.
|
|
|
|
config.pepper = <%= ActiveSupport::SecureRandom.hex(64).inspect %>
|
2009-11-09 15:43:21 -05:00
|
|
|
|
2010-01-13 13:45:24 -05:00
|
|
|
# ==> Configuration for :confirmable
|
2010-05-01 15:07:49 -04:00
|
|
|
# The time you want to give your user to confirm his account. During this time
|
2009-11-03 07:11:36 -05:00
|
|
|
# he will be able to access your application without confirming. Default is nil.
|
2010-05-01 15:07:49 -04:00
|
|
|
# When confirm_within is zero, the user won't be able to sign in without confirming.
|
|
|
|
# You can use this to let your user access some features of your application
|
|
|
|
# without confirming the account, but blocking it after a certain period
|
|
|
|
# (ie 2 days).
|
2009-11-03 07:11:36 -05:00
|
|
|
# config.confirm_within = 2.days
|
|
|
|
|
2010-01-13 13:45:24 -05:00
|
|
|
# ==> Configuration for :rememberable
|
2009-11-03 07:11:36 -05:00
|
|
|
# The time the user will be remembered without asking for credentials again.
|
|
|
|
# config.remember_for = 2.weeks
|
|
|
|
|
2010-03-26 16:52:12 -04:00
|
|
|
# ==> Configuration for :validatable
|
|
|
|
# Range for password length
|
|
|
|
# config.password_length = 6..20
|
|
|
|
|
|
|
|
# Regex to use to validate the email address
|
2010-03-28 01:15:52 -04:00
|
|
|
# config.email_regexp = /^([\w\.%\+\-]+)@([\w\-]+\.)+([\w]{2,})$/i
|
2010-03-26 16:52:12 -04:00
|
|
|
|
2010-01-13 13:45:24 -05:00
|
|
|
# ==> Configuration for :timeoutable
|
2009-11-22 19:33:19 -05:00
|
|
|
# The time you want to timeout the user session without activity. After this
|
|
|
|
# time the user will be asked for credentials again.
|
2009-11-24 21:11:49 -05:00
|
|
|
# config.timeout_in = 10.minutes
|
2009-11-22 19:19:29 -05:00
|
|
|
|
2010-01-13 13:45:24 -05:00
|
|
|
# ==> Configuration for :lockable
|
2010-03-31 05:54:11 -04:00
|
|
|
# Defines which strategy will be used to lock an account.
|
|
|
|
# :failed_attempts = Locks an account after a number of failed attempts to sign in.
|
|
|
|
# :none = No lock strategy. You should handle locking by yourself.
|
|
|
|
# config.lock_strategy = :failed_attempts
|
2009-12-30 12:19:33 -05:00
|
|
|
|
|
|
|
# Defines which strategy will be used to unlock an account.
|
|
|
|
# :email = Sends an unlock link to the user email
|
2010-05-28 07:41:13 -04:00
|
|
|
# :time = Re-enables login after a certain amount of time (see :unlock_in below)
|
2010-03-31 05:54:11 -04:00
|
|
|
# :both = Enables both strategies
|
|
|
|
# :none = No unlock strategy. You should handle unlocking by yourself.
|
2009-12-30 12:19:33 -05:00
|
|
|
# config.unlock_strategy = :both
|
|
|
|
|
2010-03-31 05:54:11 -04:00
|
|
|
# Number of authentication tries before locking an account if lock_strategy
|
|
|
|
# is failed attempts.
|
|
|
|
# config.maximum_attempts = 20
|
|
|
|
|
2009-12-30 12:19:33 -05:00
|
|
|
# Time interval to unlock the account if :time is enabled as unlock_strategy.
|
|
|
|
# config.unlock_in = 1.hour
|
|
|
|
|
2010-02-02 07:21:00 -05:00
|
|
|
# ==> Configuration for :token_authenticatable
|
|
|
|
# Defines name of the authentication token params key
|
|
|
|
# config.token_authentication_key = :auth_token
|
|
|
|
|
2010-05-16 13:13:20 -04:00
|
|
|
# ==> Scopes configuration
|
2010-01-13 13:45:24 -05:00
|
|
|
# Turn scoped views on. Before rendering "sessions/new", it will first check for
|
|
|
|
# "sessions/users/new". It's turned off by default because it's slower if you
|
|
|
|
# are using only default views.
|
|
|
|
# config.scoped_views = true
|
|
|
|
|
2010-01-06 08:31:00 -05:00
|
|
|
# By default, devise detects the role accessed based on the url. So whenever
|
|
|
|
# accessing "/users/sign_in", it knows you are accessing an User. This makes
|
|
|
|
# routes as "/sign_in" not possible, unless you tell Devise to use the default
|
|
|
|
# scope, setting true below.
|
2010-05-25 06:36:11 -04:00
|
|
|
# Note that devise does not generate default routes. You also have to
|
|
|
|
# specify them in config/routes.rb
|
2010-01-06 08:31:00 -05:00
|
|
|
# config.use_default_scope = true
|
|
|
|
|
|
|
|
# Configure the default scope used by Devise. By default it's the first devise
|
|
|
|
# role declared in your routes.
|
|
|
|
# config.default_scope = :user
|
|
|
|
|
2010-06-23 14:16:52 -04:00
|
|
|
# Configure sign_out behavior.
|
|
|
|
# By default sign_out is scoped (i.e. /users/sign_out affects only :user scope).
|
|
|
|
# In case of sign_out_scoped set to false any logout action will sign out all active scopes.
|
|
|
|
# Routes for sign_out links and redirects are same for both cases.
|
|
|
|
# You can use generic override way to reassign them (same as sign_out_path_for).
|
|
|
|
# config.sign_out_scoped = true
|
|
|
|
|
2010-05-16 13:13:20 -04:00
|
|
|
# ==> Navigation configuration
|
|
|
|
# Lists the formats that should be treated as navigational. Formats like
|
|
|
|
# :html, should redirect to the sign in page when the user does not have
|
|
|
|
# access, but formats like :xml or :json, should return 401.
|
|
|
|
# If you have any extra navigational formats, like :iphone or :mobile, you
|
|
|
|
# should add them to the navigational formats lists. Default is [:html]
|
|
|
|
# config.navigational_formats = [:html, :iphone]
|
|
|
|
|
|
|
|
# ==> Warden configuration
|
2009-11-03 07:11:36 -05:00
|
|
|
# If you want to use other strategies, that are not (yet) supported by Devise,
|
|
|
|
# you can configure them inside the config.warden block. The example below
|
|
|
|
# allows you to setup OAuth, using http://github.com/roman/warden_oauth
|
|
|
|
#
|
2009-11-03 22:34:23 -05:00
|
|
|
# config.warden do |manager|
|
2009-11-03 07:11:36 -05:00
|
|
|
# manager.oauth(:twitter) do |twitter|
|
|
|
|
# twitter.consumer_secret = <YOUR CONSUMER SECRET>
|
|
|
|
# twitter.consumer_key = <YOUR CONSUMER KEY>
|
|
|
|
# twitter.options :site => 'http://twitter.com'
|
|
|
|
# end
|
2010-03-31 16:04:48 -04:00
|
|
|
# manager.default_strategies(:scope => :user).unshift :twitter_oauth
|
2009-11-03 07:11:36 -05:00
|
|
|
# end
|
|
|
|
end
|