blocks|key|2960461|text|如果您想要与正常的注册/更新过程分开管理用户，则只需要一个用户控制器。我有一个用户控制器，以便管理员可以管理(创建，编辑，更新，删除)用户独立于正常的设备注册/更新过程。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2960462|与devise的冲突可能是因为您的路由文件中有用于设置devise的devise_for+:users+…，也有用于UsersController的resources+:users。这意味着devise和您的UsersController将尝试共享一些相同的/users路由。您需要通过更改其中一个映射到的路径来将它们分开。例如，您可以将:path+=>+'u'添加到devise_for语句中，以便设备路由映射到/u，并且不会与/users上的UsersController冲突。或者，您可以不使用devise_for+(因此仍使用/users)，而将UsersController路由更改为例如resources+:users_admin,+:controller+=>+'users'，这会将您的UsersControllers路由映射到/users_admin。请注意，这会将路径帮助器从users_path更改为users_admin_path。|offset|length|style|CODE|2960463|更新|BOLD|2960464|在你的评论/编辑之后，我快速浏览了一下教程，我认为devise基本上给了你与用户相关的功能，这些功能是从5.4节发展到9.1或9.2节的。(外加一些额外的东西，例如，电子邮件确认，密码重置，帐户锁定等)。但是，这并不意味着它是该功能的临时替代品，如果您想尝试将设计与该教程合并的话。有一些看起来可以工作的东西(例如，Devise还定义了一个current_user方法)，但路由等会有所不同，devise将事情分成更多的控制器(单独的控制器用于注册，登录/注销，密码重置…)。管理员类型的功能(如第2.2，9.3，9.4节-创建/编辑/删除/列出其他用户)是我在我的应用程序中为其添加了一个单独的UsersController。Devise没有定义UsersController，但是如果您在没有路径的情况下使用users路由，就像我上面提到的那样。|2960465|所以，更具体地说：|2960466|2960467|如果您想启用允许查看/编辑/删除所有用户的管理员类型功能，则只需要一个UsersController。|ordered-list-item|2960468|如果您想在本教程中使用devise，它可能需要一些工作来调整内容，更改页面上的帮助链接等。对不起，我没有更详细的说明；我还没有完成该教程。|2960469|2960470|您可能会错过手动完成所有这些工作所带来的额外了解，但devise是一个流行的引擎，因此了解它也是很好的。如果您有时间，您可以完全完成教程，然后再使用devise！它将帮助您了解devise在幕后所做的一些事情。附言:即使你不能立即完全理解，看一下设计的源代码也是很有指导意义的。|2960471|entityMap^0|0|Y|J|22|G|3L|6|4P|C|54|A|5R|2|5Z|6|6Y|A|7F|6|8B|1A|AC|C|B2|A|BF|G|0|0|2|0|4Q|C|9W|5|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|10|8|@$D|11|E|12|F|G]|$D|13|E|14|F|G]|$D|15|E|16|F|G]|$D|17|E|18|F|G]|$D|19|E|1A|F|G]|$D|1B|E|1C|F|G]|$D|1D|E|1E|F|G]|$D|1F|E|1G|F|G]|$D|1H|E|1I|F|G]|$D|1J|E|1K|F|G]|$D|1L|E|1M|F|G]|$D|1N|E|1O|F|G]|$D|1P|E|1Q|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|1R|8|@$D|1S|E|1T|F|J]]|9|@]|A|$]]|$1|K|3|L|5|6|7|1U|8|@$D|1V|E|1W|F|G]|$D|1X|E|1Y|F|G]]|9|@]|A|$]]|$1|M|3|N|5|6|7|1Z|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|20|8|@]|9|@]|A|$]]|$1|P|3|Q|5|R|7|21|8|@]|9|@]|A|$]]|$1|S|3|T|5|R|7|22|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|23|8|@]|9|@]|A|$]]|$1|V|3|W|5|6|7|24|8|@]|9|@]|A|$]]|$1|X|3|-4|5|6|7|25|8|@]|9|@]|A|$]]]|Y|$]]

You only need a users controller if you want to manage users separately from the normal signup/update process. I have a users controller so that admins can manage (create, edit, update, delete) users independently of the normal devise signup/update process.

The conflict with devise is probably because you have <code>devise_for :users …</code> in your routes file to set up devise and also have <code>resources :users</code> for your UsersController. This means that devise and your UsersController will be trying to share some of the same <code>/users</code> routes. You need to separate them out by changing the path that one of them is mapped to. You could either add, for example, <code>:path =&gt; 'u'</code> to your <code>devise_for</code> statement so that devise routes are mapped to <code>/u</code> and won't conflict with your UsersController on <code>/users</code>. Alternatively you could leave the <code>devise_for</code> alone (therefore still using <code>/users</code>) and instead change your UsersController routing to, for example, <code>resources :users_admin, :controller =&gt; 'users'</code> which would move your UsersControllers routes to be mapped to <code>/users_admin</code>. Note that this would change the path helpers from, for example, <code>users_path</code> to <code>users_admin_path</code>.

UPDATE

Following your comment/edit, I've had a quick look at the tutorial and I think that devise basically gives you the equivalent functionality of the user-related functionality which is developed from section 5.4 to about sections 9.1 or 9.2. (plus some extra stuff, for example, email confirmation, password reset, account lockout etc.). However, that doesn't mean that it's a drop-in replacement for that functionality, if you want to try and merge Devise with that tutorial. There are some things that look like they would work (e.g. Devise also defines a <code>current_user</code> method), but the routes etc. would be different, and devise splits things up into more controllers (separate controllers for registration, sign in/out, password reset…). The admin-type functionality (like in sections 2.2, 9.3, 9.4 - create/edit/delete/list other users) is what I've added a separate UsersController for in my app. Devise doesn't define a UsersController, but does use the <code>users</code> routes if you do <code>devise_for :users</code> without a path as I mentioned above.

So, more specifically:

<ol>
<li>You would only need a UsersController if you want to enable admin-type functionality allowing viewing/editing/deleting all users.</li>
<li>If you wanted to use devise in the tutorial, it would probably need some work to massage things to fit, changing helper links on pages etc. Sorry I'm not more specific; I haven't done that tutorial.</li>
</ol>

You would be missing out on the extra understanding that comes from doing it all manually yourself, but devise is a popular engine, so it's good to know as well. If you have the time, you could do the tutorial entirely, and then again with devise! It would help you understand some of the kind of stuff devise is doing behind the scenes. P.S: It can be instructive to look at the devise source code, even if you don't understand it all immediately.

I am a Rails newbie. I am working on a small Rails4 project trying to improve my skills.
I am loosely following <a href="http://www.railstutorial.org/book">M.Hartl's tutorial</a>.

As per the tutorial a custom user authentication is built.
However I would like to use Devise for User authentication.
Do I still need to have a Users controller as in the tutorial?
In which cases should I use/not use a Users controller when already using Devise?

Concerning the tutorial, do I just skip the controller generating part or do I have to map the actions to Devise?

Do I need a "Users" controller when using Devise in Rails

我是Rails新手。我正在做一个小型的Rails4项目，试图提高我的技能。我正在松散地关注。根据本教程，将构建自定义用户身份验证。但是，我想使用Devise进行用户身份验证。我是否仍然需要像本教程中那样拥有用户控制器？在哪些情况下，我应该在已经使用Devise的情况下使用/不使用用户控制器？关于本教程，我是直接跳过控制...

问在Rails中使用Devise时是否需要"Users“控制器
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在Rails中使用Devise时是否需要"Users“控制器EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在Rails中使用Devise时是否需要"Users“控制器
EN