rails devise 实例

2023-10-19 15:40
文章标签 实例 rails devise

本文主要是介绍rails devise 实例,希望对大家解决编程问题提供一定的参考价值,需要的开发者们随着小编来一起学习吧!

前言:

上两节我们讲了用户的添加、登录……,这一次我们遵循Rails的理念,快速实现用户的注册、登录……

理念:

1、少就是多

2、不要重复制造轮子

开始:

1、新建rails工程

?
1
$ rails new r2 -d=mysql

配置Gemfile文件,添加一句:

?
1
gem 'devise'             #devise是一个gem包

配置config/database.yml文件,修改适合自己的数据库名、用户名和密码。

?
1
$ bundle install
?
1
$ rake db :create         #创建数据库

解释:

  1. devise是一个开源的工程,主要用于用户的注册、登录、找回密码、session等等。所谓“不要重复制造轮子”,既然有好的工程,我们就拿来用,直接在Gemfile中作为gem包引入,方便之极。Do you want to know more? https://github.com/plataformatec/devise

2、配置devise

(1)应用devise:

?
1
$ rails g devise :install

输出如下:

?
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
===============================================================================
Some setup you must do manually if you haven't yet:
   1 . Setup default url options for your specific environment. Here is an
      example of development environment:
        config.action_mailer.default_url_options = { :host => 'localhost:3000' }
      This is a required Rails configuration. In production it must be the
      actual host of your application
   2 . Ensure you have defined root_url to *something* in your config/routes.rb.
      For example:
        root :to => "home#index"
   3 . Ensure you have flash messages in app/views/layouts/application.html.erb.
      For example:
        <p class = "notice" ><%= notice %></p>
        <p class = "alert" ><%= alert %></p>
===============================================================================

以上提示,我们后面再做理会!

(2)使用devise创建user model:

?
1
$ rails g devise User

发生了什么?

  1. 在app/models文件夹下产生了一个user.rb,也就是创建了一个user model
  2. 在db/migrate文件夹下产生了一个migrate文件
  3. 在config/routes.rb文件中添加了一行 devise_for :users

(3)配置user

编辑app/models/user.rb文件

?
1
2
3
4
5
6
7
8
9
10
class User < ActiveRecord::Base
   # Include default devise modules. Others available are:
   # :token_authenticatable, :encryptable, :confirmable, :lockable, :timeoutable and :omniauthable
   devise :database_authenticatable , :registerable ,
          :recoverable , :rememberable , :trackable , :validatable ,     #末尾添加,号
          :confirmable , :lockable                 #添加这一行
   # Setup accessible (or protected) attributes for your model
   attr_accessible :email , :password , :password_confirmation , :remember_me
end

编辑db/migrate/20110726xxxxxx_devise_create_users.rb文件

?
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
class DeviseCreateUsers < ActiveRecord::Migration
   def self .up
     create_table( :users ) do |t|
       t.database_authenticatable :null => false
       t.recoverable
       t.rememberable
       t.trackable
       #添加以下两行
       t.confirmable
       t.lockable :lock_strategy => :failed_attempts , :unlock_strategy => :both
       # t.encryptable
       # t.confirmable
       # t.lockable :lock_strategy => :failed_attempts, :unlock_strategy => :both
       # t.token_authenticatable
       t.timestamps
     end
     add_index :users , :email ,                :unique => true
     add_index :users , :reset_password_token , :unique => true
     #添加以下两行
     add_index :users , :confirmation_token ,   :unique => true
     add_index :users , :unlock_token ,         :unique => true
     # add_index :users, :confirmation_token,   :unique => true
     # add_index :users, :unlock_token,         :unique => true
     # add_index :users, :authentication_token, :unique => true
   end
   def self .down
     drop_table :users
   end
end

生成数据表:

?
1
$ rake db :migrate

(3)配置邮件服务器

编辑config/initializers/devise.rb

?
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
# 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|
   # ==> Mailer Configuration
   # Configure the e-mail address which will be shown in DeviseMailer.
   config.mailer_sender = "xxx@126.com"   #换成你的邮箱,最好不要是gmail
   # Configure the class responsible to send e-mails.
   # config.mailer = "Devise::Mailer"
   # ==> ORM configuration
   # Load and configure the ORM. Supports :active_record (default) and
   # :mongoid (bson_ext recommended) by default. Other ORMs may be
   # available as additional gems.
   require 'devise/orm/active_record'
   # ==> Configuration for any authentication mechanism
   # Configure which keys are used when authenticating a user. The default is
   # just :email. You can configure it to use [:username, :subdomain], so for
   # authenticating a 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.
   # You can also supply a hash where the value is a boolean determining whether
   # or not authentication should be aborted when the value is not present.
   # config.authentication_keys = [ :email ]
   # Configure parameters from the request object used for authentication. Each entry
   # given should be a request method and it will automatically be passed to the
   # find_for_authentication method and considered in your model lookup. For instance,
   # if you set :request_keys to [:subdomain], :subdomain will be used on authentication.
   # The same considerations mentioned for authentication_keys also apply to request_keys.
   # config.request_keys = []
   # Configure which authentication keys should be case-insensitive.
   # These keys will be downcased upon creating or modifying a user and when used
   # to authenticate or find a user. Default is :email.
   config.case_insensitive_keys = [ :email ]
   
   # Configure which authentication keys should have whitespace stripped.
   # These keys will have whitespace before and after removed upon creating or
   # modifying a user and when used to authenticate or find a user. Default is :email.
   config.strip_whitespace_keys = [ :email ]
   # Tell if authentication through request.params is enabled. True by default.
   # config.params_authenticatable = true
   # Tell if authentication through HTTP Basic Auth is enabled. False by default.
   # config.http_authenticatable = false
   # If http headers should be returned for AJAX requests. True by default.
   # config.http_authenticatable_on_xhr = true
   # The realm used in Http Basic Authentication. "Application" by default.
   # config.http_authentication_realm = "Application"
   # It will change confirmation, password recovery and other workflows
   # to behave the same regardless if the e-mail provided was right or wrong.
   # Does not affect registerable.
   # config.paranoid = true
   # ==> Configuration for :database_authenticatable
   # 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
   # Setup a pepper to generate the encrypted password.
   # config.pepper = "025e837f7ae23e7f4e3b0a3dd048577e3b82c0f803fc4a8bac896303ab40545ab6e47600962cd8075c3122af0c98dba62bd6399604d622579797c282b0b1b2a1"
   # ==> Configuration for :confirmable
   # The time you want to give your user to confirm his account. During this time
   # he will be able to access your application without confirming. Default is 0.days
   # 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).
   # config.confirm_within = 2.days
   # Defines which key will be used when confirming an account
   # config.confirmation_keys = [ :email ]
   # ==> Configuration for :rememberable
   # The time the user will be remembered without asking for credentials again.
   # config.remember_for = 2.weeks
   # If true, a valid remember token can be re-used between multiple browsers.
   # config.remember_across_browsers = true
   # If true, extends the user's remember period when remembered via cookie.
   # config.extend_remember_period = false
   # If true, uses the password salt as remember token. This should be turned
   # to false if you are not using database authenticatable.
   config.use_salt_as_remember_token = true
   # Options to be passed to the created cookie. For instance, you can set
   # :secure => true in order to force SSL only cookies.
   # config.cookie_options = {}
   # ==> Configuration for :validatable
   # Range for password length. Default is 6..128.
   # config.password_length = 6..128
   # Regex to use to validate the email address
   # config.email_regexp = /\A([\w\.%\+\-]+)@([\w\-]+\.)+([\w]{2,})\z/i
   # ==> Configuration for :timeoutable
   # The time you want to timeout the user session without activity. After this
   # time the user will be asked for credentials again. Default is 30 minutes.
   # config.timeout_in = 30.minutes
   # ==> Configuration for :lockable
   # 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
   # Defines which key will be used when locking and unlocking an account
   # config.unlock_keys = [ :email ]
   # Defines which strategy will be used to unlock an account.
   # :email = Sends an unlock link to the user email
   # :time  = Re-enables login after a certain amount of time (see :unlock_in below)
   # :both  = Enables both strategies
   # :none  = No unlock strategy. You should handle unlocking by yourself.
   # config.unlock_strategy = :both
   # Number of authentication tries before locking an account if lock_strategy
   # is failed attempts.
   # config.maximum_attempts = 20
   # Time interval to unlock the account if :time is enabled as unlock_strategy.
   # config.unlock_in = 1.hour
   # ==> Configuration for :recoverable
   #
   # Defines which key will be used when recovering the password for an account
   # config.reset_password_keys = [ :email ]
   # Time interval you can reset your password with a reset password key.
   # Don't put a too small interval or your users won't have the time to
   # change their passwords.
   config.reset_password_within = 2 .hours
   # ==> Configuration for :encryptable
   # Allow you to use another encryption algorithm besides bcrypt (default). You can use
   # :sha1, :sha512 or 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 (then you should set stretches to 10, and copy
   # REST_AUTH_SITE_KEY to pepper)
   # config.encryptor = :sha512
   # ==> Configuration for :token_authenticatable
   # Defines name of the authentication token params key
   # config.token_authentication_key = :auth_token
   # If true, authentication through token does not store user in session and needs
   # to be supplied on each request. Useful if you are using the token as API token.
   # config.stateless_token = false
   # ==> Scopes configuration
   # Turn scoped views on. Before rendering "sessions/new", it will first check for
   # "users/sessions/new". It's turned off by default because it's slower if you
   # are using only default views.
   # config.scoped_views = false
   # Configure the default scope given to Warden. By default it's the first
   # devise role declared in your routes (usually :user).
   # config.default_scope = :user
   # Configure sign_out behavior.
   # Sign_out action can be scoped (i.e. /users/sign_out affects only :user scope).
   # The default is true, which means any logout action will sign out all active scopes.
   # config.sign_out_all_scopes = true
   # ==> 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.
   #
   # The :"*/*" and "*/*" formats below is required to match Internet
   # Explorer requests.
   # config.navigational_formats = [:"*/*", "*/*", :html]
   # The default HTTP method used to sign out a resource. Default is :delete.
   config.sign_out_via = :delete
   # ==> OmniAuth
   # Add a new OmniAuth provider. Check the wiki for more information on setting
   # up on your models and hooks.
   # config.omniauth :github, 'APP_ID', 'APP_SECRET', :scope => 'user,public_repo'
   # ==> Warden configuration
   # If you want to use other strategies, that are not supported by Devise, or
   # change the failure app, you can configure them inside the config.warden block.
   #
   # config.warden do |manager|
   #   manager.failure_app   = AnotherApp
   #   manager.intercept_401 = false
   #   manager.default_strategies(:scope => :user).unshift :some_external_strategy
   # end
end

编辑config/environments/development.rb

?
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
R2 ::Application.configure do
   # Settings specified here will take precedence over those in config/application.rb
   # In the development environment your application's code is reloaded on
   # every request.  This slows down response time but is perfect for development
   # since you don't have to restart the webserver when you make code changes.
   config.cache_classes = false
   # Log error messages when you accidentally call methods on nil.
   config.whiny_nils = true
   # Show full error reports and disable caching
   config.consider_all_requests_local       = true
   config.action_view.debug_rjs             = true
   config.action_controller.perform_caching = false
   # Don't care if the mailer can't send
   config.action_mailer.raise_delivery_errors = true  #此处改为true
   #添加以下内容
   config.action_mailer.default_url_options = { :host => "localhost:3000" } #刚才devise的提示中提到这一句
   config.action_mailer.delivery_method = :smtp
   config.action_mailer.smtp_settings = {
     :address => "smtp.126.com" ,
     :port => 25 ,
     :domain => "126.com" ,
     :authentication => :login ,
     :user_name => "xxx@126.com" , #你的邮箱
     :password => "xxxxxx" #你的密码
   }
   # Print deprecation notices to the Rails logger
   config.active_support.deprecation = :log
   # Only use best-standards-support built into browsers
   config.action_dispatch.best_standards_support = :builtin
end

(4)其它配置

随便新建一个home controller

?
1
$ rails g controller home index

删除public目录下的index.html文件

修改config/routes.rb文件,添加一句

?
1
root :to => "home#index"

编辑app/controllers/home_controller.rb文件

?
1
2
3
4
5
6
7
class HomeController < ApplicationController
   before_filter :authenticate_user #添加这一句
   
   def index
   end
end

编辑app/views/layouts/application.html.erb文件

?
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
<! DOCTYPE html>
<html>
<head>
   <title> R2 </title>
   <%= stylesheet_link_tag :all %>
   <%= javascript_include_tag :defaults %>
   <%= csrf_meta_tag %>
</head>
<body>
#添加以下两句
<p class = "notice" ><%= notice %></p>
<p class = "alert" ><%= alert %></p>
<%= yield %>
</body>
</html>

3、运行程序

启动工程:

?
1
$ rails s

浏览器输入:http://localhost:3000

结果转到了http://localhost:3000/users/sign_in,要求你登录

我没有账户登录怎么办?点击sign_up注册账户

填写email、密码,点击“sign up ”,不出意外的话去注册邮箱收取确认邮件吧!

点一下链接:

一个注册、登录程序就完成了!!!



devise.rb文件 sender一定要改成你自己的邮箱名字


这篇关于rails devise 实例的文章就介绍到这儿,希望我们推荐的文章对编程师们有所帮助!



http://www.chinasem.cn/article/240763

相关文章

Python实例题之pygame开发打飞机游戏实例代码

《Python实例题之pygame开发打飞机游戏实例代码》对于python的学习者,能够写出一个飞机大战的程序代码,是不是感觉到非常的开心,:本文主要介绍Python实例题之pygame开发打飞机... 目录题目pygame-aircraft-game使用 Pygame 开发的打飞机游戏脚本代码解释初始化部

Spring组件实例化扩展点之InstantiationAwareBeanPostProcessor使用场景解析

《Spring组件实例化扩展点之InstantiationAwareBeanPostProcessor使用场景解析》InstantiationAwareBeanPostProcessor是Spring... 目录一、什么是InstantiationAwareBeanPostProcessor?二、核心方法解

java String.join()方法实例详解

《javaString.join()方法实例详解》String.join()是Java提供的一个实用方法,用于将多个字符串按照指定的分隔符连接成一个字符串,这一方法是Java8中引入的,极大地简化了... 目录bVARxMJava String.join() 方法详解1. 方法定义2. 基本用法2.1 拼接

Linux lvm实例之如何创建一个专用于MySQL数据存储的LVM卷组

《Linuxlvm实例之如何创建一个专用于MySQL数据存储的LVM卷组》:本文主要介绍使用Linux创建一个专用于MySQL数据存储的LVM卷组的实例,具有很好的参考价值,希望对大家有所帮助,... 目录在Centos 7上创建卷China编程组并配置mysql数据目录1. 检查现有磁盘2. 创建物理卷3. 创

Java List排序实例代码详解

《JavaList排序实例代码详解》:本文主要介绍JavaList排序的相关资料,Java排序方法包括自然排序、自定义排序、Lambda简化及多条件排序,实现灵活且代码简洁,文中通过代码介绍的... 目录一、自然排序二、自定义排序规则三、使用 Lambda 表达式简化 Comparator四、多条件排序五、

Java实例化对象的​7种方式详解

《Java实例化对象的​7种方式详解》在Java中,实例化对象的方式有多种,具体取决于场景需求和设计模式,本文整理了7种常用的方法,文中的示例代码讲解详细,有需要的可以了解下... 目录1. ​new 关键字(直接构造)​2. ​反射(Reflection)​​3. ​克隆(Clone)​​4. ​反序列化

Python解决雅努斯问题实例方案详解

《Python解决雅努斯问题实例方案详解》:本文主要介绍Python解决雅努斯问题实例方案,雅努斯问题是指AI生成的3D对象在不同视角下出现不一致性的问题,即从不同角度看物体时,物体的形状会出现不... 目录一、雅努斯简介二、雅努斯问题三、示例代码四、解决方案五、完整解决方案一、雅努斯简介雅努斯(Janu

Python开发文字版随机事件游戏的项目实例

《Python开发文字版随机事件游戏的项目实例》随机事件游戏是一种通过生成不可预测的事件来增强游戏体验的类型,在这篇博文中,我们将使用Python开发一款文字版随机事件游戏,通过这个项目,读者不仅能够... 目录项目概述2.1 游戏概念2.2 游戏特色2.3 目标玩家群体技术选择与环境准备3.1 开发环境3

Vue3组件中getCurrentInstance()获取App实例,但是返回null的解决方案

《Vue3组件中getCurrentInstance()获取App实例,但是返回null的解决方案》:本文主要介绍Vue3组件中getCurrentInstance()获取App实例,但是返回nu... 目录vue3组件中getCurrentInstajavascriptnce()获取App实例,但是返回n

SQL表间关联查询实例详解

《SQL表间关联查询实例详解》本文主要讲解SQL语句中常用的表间关联查询方式,包括:左连接(leftjoin)、右连接(rightjoin)、全连接(fulljoin)、内连接(innerjoin)、... 目录简介样例准备左外连接右外连接全外连接内连接交叉连接自然连接简介本文主要讲解SQL语句中常用的表