README.md in dailycred-0.1.4 vs README.md in dailycred-0.1.5
- old
+ new
@@ -1,7 +1,9 @@
# Dailycred
+[](https://travis-ci.org/dailycred/dailycred)
+
## Introduction
The Dailycred ruby gem is everything you need to get off the ground running with robust authentication. It includes an [omniauth](https://github.com/intridea/omniauth) provider and a generator to create necessary models and controllers. The generated authentication structure is inspired by [nifty-generators](https://github.com/ryanb/nifty-generators). To get started using Dailycred with Ruby on Rails, the first thing you need to do is add the dailycred gem to your gemfile:
gem 'dailycred'
@@ -54,11 +56,11 @@
To use a social sign-in service instead of email, and password, use `connect_path.`
<%= link_to 'sign in with facebook', connect_path(:identity_provider => :facebook) %>
-The `identity_provider` can be one of `facebook`, `google`, or `twitter.`
+The `identity_provider` can be one of `facebook`, `google`, `twitter`, `disqus`, or `instagram`.
After a user has social connected, their social data is serialized into individual fields in the user model. The serialized object is the exact same as what the social provider's graph response returns. For example:
p current_user.facebook
# =>
@@ -158,10 +160,10 @@
#### Testing Controllers
Testing controllers that have the `authenticate` before filter is easy:
# with mocha
- @controller.expects(:current_user).returns(@user)
+ @controller.stubs(:current_user).returns(@user)
See `dummy/test/functional/post_controller_test.rb` for an example.
#### Dailycred API