Please read for an updated status on RailsCasts:
Learn more or hide this
GitHub User: stib
Thanks for another great screencast Ryan!
I am running into a routing error that I am not sure how to solve - feels like I am missing something obvious as I don't see anyone else reporting this.
When I go to 127.0.0.1:3000/auth/twitter I get a
No route matches "/auth/twitter"
I have the "gem omniauth" in my gemfile (and installed through bundler) and I have omniauth.rb where I have setup twitter connection as suggested.
The server starts up fine - the home page loads. I am on Ruby
1.9.2p180 and Rails 3.0.5 on a Win box.
How does this /auth/twitter route get interpreted? Does Omniauth do it behind the scenes somehow by extending the routes.rb?
Thanks for any thoughts or pointers.