I came across this great site for the Ruby on Rails API: http://railsapi.com
Monthly Archive for May, 2009
I’ve been playing around rspec in my application which also uses AuthLogic’s OpenID. When doing
If there’s one thing I can’t stand in the development process it’s writing code to save data. In fact, there are only a few things which I’d consider more useless than dealing with data persistence- one of them being data migration. I hate dealing with persistence because it’s totally mundane and repetitive code. Worse, nobody outside of IT really understands the details of persistence. Which means it has no business value. And why should users care about unit of work or active record vs. repository? Should saving an object really be that complicated of a task? Absolutely not. Which is why no one cares. It’s like caring about how your beer was delivered. Really, I just want to drink the damn beer. Yet somehow the thing which should be a no brainer takes the most time and effort to do. And causes the most debate. And causes the most problems. However, I recently got my first glimmer of hope- a cloud with a silver lining- that maybe, just maybe, someday, we’ll actually have simple data access.
So, I’m working on a Rails App and I want to use OpenID (and only OpenID) for authentication. I was going to use Restful_Authentication with the open_id_authentication extension, but then I saw Ryan Bates’ Railscast on AuthLogic. Authlogic has an OpenID extention which looked perfect for my needs, and Authlogic seemed like a great gem for authentication. My goal was simple: I wanted to support, and only support, authentication via OpenID. None of this username/password/salt stuff.
