{"id":2480,"date":"2012-01-27T14:15:40","date_gmt":"2012-01-27T16:15:40","guid":{"rendered":"http:\/\/blog.plataformatec.com.br\/?p=2480"},"modified":"2012-03-08T10:05:10","modified_gmt":"2012-03-08T13:05:10","slug":"devise-2-0-released","status":"publish","type":"post","link":"https:\/\/blog.plataformatec.com.br\/2012\/01\/devise-2-0-released\/","title":{"rendered":"Devise 2.0 released"},"content":{"rendered":"
We have just released Devise 2.0<\/a>. This version is not a big refactoring, nor contains stellar features, it is simply another step towards a very mature authentication library.<\/p>\n Over the years, we have learned from our own experience and from your feedback, how to better use Devise. We’ve made changes to improve security and also to make the library more flexible. All those changes were backwards compatible, forcing us to maintain different branches of logic in the same source code to accomodate those different scenarios. Devise 2.0 simply deprecates those old scenarios so we can clean up the code.<\/p>\n When you migrate to 2.0, you should get some warnings. The amount of warnings will depend on when you started using Devise. For recent applications, it should take 2 minutes to update (basically fixing up migrations and the locale file), older applications should be up to speed in 15-30 minutes. We have created a page with instructions to upgrade, be sure to read it for a smoother experience<\/a>.<\/p>\n Finally, Devise 2.0 also includes:<\/p>\n\n
t.database_authenticatable<\/code> and friends in migrations in favor of explicit code;<\/li>\n
config.parent_controller<\/code> which you can set to something different from
ApplicationController<\/code>. There is a good sample engine here<\/a>;<\/li>\n