«
»

archived blog posts

Why restful_authentication RoR plugin is cool

02.13.09 | Comment?

Let me just cite some reasons why this plugin is so cool!

1.)It generates your registration page, and login page. You can opt for the user activation, hashing passwords.

2.)You may also integrate role_requirement plugin with restful_authentication plugin if you want user roles or even MULTIPLE user Roles! (A big thanks to Greg Moreno for telling me about this plugin!)

3.)makes your user registration , login, and (optionally,) activation easier to build within your app!

If you want to try it out, you may do ,

script/plugin install git://github.com/technoweenie/restful-authentication.git

to start integrating the plugin,

script/generate authenticated user sessions  [*args]

[ *args] are simply options you might need to specify if, (This is part of the README.textfile of the plugin)

user is the controller name for your users,

sessions is the controller name for your sessions controller,This is the
  controller that handles the actual login/logout function on the site.

* –include-activation: Generates the code for a ActionMailer and its respective
  Activation Code through email.

* –stateful: Builds in support for acts_as_state_machine and generates
  activation code.  (@–stateful@ implies @–include-activation@). Based on the
  idea at [[http://www.vaporbase.com/postings/stateful_authentication]]. Passing
  @–skip-migration@ will skip the user migration, and @–skip-routes@ will skip
  resource generation — both useful if you’ve already run this generator.
  (Needs the “acts_as_state_machine plugin”:http://elitists.textdriven.com/svn/plugins/acts_as_state_machine/,
  but new installs should probably run with @–aasm@ instead.)

* –aasm: Works the same as stateful but uses the “updated aasm gem”:http://github.com/rubyist/aasm/tree/master
 
* –rspec: Generate RSpec tests and Stories in place of standard rails tests.
  This requires the
    “RSpec and Rspec-on-rails plugins”:http://rspec.info/
  (make sure you “./script/generate rspec” after installing RSpec.)  The rspec
  and story suite are much more thorough than the rails tests, and changes are
  unlikely to be backported.
 
* –old-passwords: Use the older password scheme (see [[#COMPATIBILITY]], above)

* –skip-migration: Don’t generate a migration file for this model

* –skip-routes: Don’t generate a resource line in @config/routes.rb@

btw, PhRUG is going to have their monthly meet up @ Exist Tech bar on Feb. 19, 2009 from 6:30pm to 9:30pm.
You will have to signup so you will be allowed by the guard at the building entrance to let you in or you will have to give your ID.  They will have 2 speakers: Mikong will present Rails and CouchDB and Marco Palinar will be talking about HAML / CSS and Rails Views. Hope to see you there!

Comments are closed.


«
»