dailycred 0.1.461 → 0.2.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+!binary "U0hBMQ==":
+  metadata.gz: 347a55fb9eae49897183cd5bab9ba6b7316c6215
+  data.tar.gz: ca8ce17bab65de8228d0898cc509b8301ed0bed7
+!binary "U0hBNTEy":
+  metadata.gz: a463c7d68d9a0264595d7b76a2bf4bf4a1d0ef838c93274630352b96ec8f1f05569d2c0dfebb2a37bc1af43304d735f4a0f302c40f999e225542cef2691a3bdf
+  data.tar.gz: f496ca9d9213cef0b0a390bf78865d4d363dbd002aaaafb46be0d6e053bde5fdbd7b93159648c1868d78eba882a1e980aed4e220164a9cb504a71769d8093731

data/Gemfile

@@ -1,9 +1,8 @@
 source 'https://rubygems.org'
 
 gemspec
-
 gem 'rspec'
-gem 'rails'
+gem 'rails', '~> 3.2.12'
 gem 'simplecov'
 gem 'ruby_gntp'
 gem 'growl'
@@ -16,3 +15,4 @@ gem 'fl-rocco'
 gem 'redcarpet', '~> 1.17'
 gem 'markdown'
 gem 'maruku'
+gem 'faraday'

data/README.md

@@ -1,10 +1,12 @@
-# Dailycred
+## Ruby on Rails
 
-[![Build Status](https://secure.travis-ci.org/dailycred/dailycred.png?branch=master)](https://travis-ci.org/dailycred/dailycred)
+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). 
 
-## Introduction
+If you'd rather only communicate with Dailycred through OAuth and provide your own authentication controllers and models, you can use the [omniauth_dailycred](https://github.com/dailycred/omniauth_dailycred) gem.
 
-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:
+##Installation
+
+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'
 
@@ -30,21 +32,21 @@ While this is enough to get off the ground running with user authentication, thi
 
 ## Authenticating
 
-#### login_path
+### login_path
 
 A helper for linking to the authentication url.
 
     <%= link_to 'sign up', login_path %>
     # => <a href="/auth/dailycred">sign up</a>
 
-#### logout_path
+### logout_path
 
 To logout a user, simply send them to `/auth/logout`.
 
     <%= link_to 'logout', logout_path %>
     # => <a href="/auth/logout">logout</a>
     
-#### authenticate
+### authenticate
 
 To protect a controller method from unauthorized users, use the 'authorize' helper method as a `before_filter`.
 
@@ -111,7 +113,7 @@ You can also connect additional social accounts to an existing user:
 
 There are a few other helper methods available:
 
-#### current_user
+### current_user
 
 Returns the current logged in user or nil. Example usage:
 
@@ -119,7 +121,7 @@ Returns the current logged in user or nil. Example usage:
       redirect_to :controller => 'welcome', :action => 'thanks'
     end
 
-#### dailycred
+### dailycred
 
 A helper for instantiating a dailycred client instance. Use as a `before_filter` to load a @dailycred instance variable, or just use it as a helper method. Example usage:
 
@@ -137,27 +139,27 @@ or just as a helper
         dailycred.event(current_user.uid, "New Task", @task.name)
     end
 
-#### Tagging a User
+### Tagging a User
 
 Dailycred provides the ability to 'tag' users, whether for reference in analytics or any other reason. Note that this is a very simple 'tagging' system, and not something you should use for dynamic tagging situations in your application.
 
     @user.tag 'awesome'
     @user.untag 'awesome'
 
-#### Firing Events
+### Firing Events
 
 You can also fire events tied to a specific user - this is helpful for goal tracking and tying actions to a specific user in analytics. We already fire many events for when a user signs up, resets a password, and much more, but you can also use the event system for something more specific for your application.
 
     # user#fire_event(key, value)
     @user.fire_event 'task added', @task.name
 
-#### Building Referral URLs
+### Building Referral URLs
 
 To easily build referral URLs to track sharing amongst your users, use `referral_link(my_site)`, where *my_site* is the url that you wish referred users to be sent to.
 
     current_user.referral_link("http://www.mysite.com")
 
-#### Testing Controllers
+### Testing Controllers
 
 Testing controllers that have the `authenticate` before filter is easy:
 
@@ -166,7 +168,7 @@ Testing controllers that have the `authenticate` before filter is easy:
 
 See `dummy/test/functional/post_controller_test.rb` for an example.
 
-#### Dailycred API
+### Dailycred API
 
 For reference, have a look at the [annotated source code.](https://www.dailycred.com/public/docs/ruby/lib/dailycred.html)
 
@@ -181,7 +183,32 @@ Where opts is an optional hash for passing options. After initializing your clie
     @dailycred.untag(current_user.uid, "Failed Checkout") # user_id, key
 
 
-#### Configuration
+### Persona Login
+
+1. Set your `persona audience` in your [dailycred identity provider settings](https://www.dailycred.com/admin/settings/identity-providers). This will be `http://{your-url}/auth/dailycred/callback`.
+2. Make sure you have configured your `callback url` in your [dailycred app settings](https://www.dailycred.com/admin/settings)
+3. In `config/omniauth.rb`, configure your middleware options to include your persona audience:
+
+    Rails.configuration.DAILYCRED_OPTIONS = {
+        middleware: {
+            persona_audience = "http://{your-url}/auth/dailycred/callback"
+        }
+    }
+
+4. In your javascript, call `personaLogin()`.
+
+    $(document).ready(function(){
+        $('.persona-login').click(function(){
+            personaLogin();
+        })
+    })
+
+5. Your user will be redirected to your [persona.org](https://persona.org) to login. If successful, your user will be redirected to your OAuth callback URL and be logged in.
+
+For more details, visit our [persona documentation](https://www.dailycred.com/docs/persona)
+
+
+### Configuration
 
 To specify where users should be redirected after authentication actions, setup configure an `after_auth` property on a `Rails.configuration.DAILYCRED_OPTIONS` variable. Example:
 
@@ -202,3 +229,4 @@ To specify where users should be redirected after authentication actions, setup
 
 ![](https://www.dailycred.com/dc.gif?client_id=dailycred&title=rails_repo "dailycred")
 
+[![Build Status](https://secure.travis-ci.org/dailycred/dailycred.png?branch=master)](https://travis-ci.org/dailycred/dailycred)

data/Rakefile

@@ -27,7 +27,7 @@ task :docs do
     require 'fileutils'
     require 'maruku'
     Rocco::make 'docs/'
-    FileUtils.cp_r "docs/lib/", "/Users/hank/rails/dailycred/public/docs/ruby/", :verbose => true
+    FileUtils.cp_r "docs/lib/", "/Users/hank/java/dailycred/public/docs/ruby/", :verbose => true
     md = ""
     File.open("README.md", "r") do |infile|
       while (line = infile.gets)
@@ -35,7 +35,7 @@ task :docs do
       end
     end
     doc = Maruku.new(md)
-    File.open("/Users/hank/rails/dailycred/app/views/tags/ruby.html", 'w') {|f| f.write doc.to_html}
+    File.open("/Users/hank/java/dailycred/app/views/tags/docs/rubyonrails.html", 'w') {|f| f.write doc.to_html}
   rescue LoadError
     warn "#$! -- rocco tasks not loaded."
     task :rocco

data/app/controllers/sessions_controller.rb

@@ -26,6 +26,6 @@ class SessionsController < ApplicationController
   private
 
   def auth_hash
-    request.env['omniauth.auth']
+    h = request.env['omniauth.auth']
   end
 end

data/app/views/sessions/info.html.erb

@@ -9,5 +9,5 @@
   <%= link_to 'Log In', login_path() %>
   <br><%= link_to 'connect with facebook', connect_path(:identity_provider => :facebook) %>
   <br><%= link_to 'connect with google', connect_path(:identity_provider => :google) %>
-  <br><%= link_to 'connect with twitter', current_user.connect_path(:twitter) %>
-<% end %>
+  <br><%= link_to 'connect with twitter',connect_path(:identity_provider => :twitter) %>
+<% end %>

data/config/routes.rb

@@ -1,7 +1,7 @@
 Dailycred::Engine.routes.draw do
-  match "/:provider/callback" => "sessions#create"
-  match "/logout" => "sessions#destroy", :as => :logout
-  match "/" => "sessions#info", :as => :auth_info
+  get "/:provider/callback" => "sessions#create"
+  get "/logout" => "sessions#destroy", :as => :logout
+  get "/" => "sessions#info", :as => :auth_info
   # get "/dailycred", :as => :login
-  match "/failure" => "sessions#failure"
+  get "/failure" => "sessions#failure"
 end

data/dailycred.gemspec

@@ -6,7 +6,7 @@ Gem::Specification.new do |gem|
   gem.email         = ["hstove@gmail.com"]
   gem.description   = %q{A Ruby on Rails engine for authentication with Dailycred.}
   gem.summary       = %q{}
-  gem.homepage      = "https://www.dailycred.com"
+  gem.homepage      = "https://github.com/dailycred/dailycred"
   gem.add_dependency("omniauth")
   gem.add_dependency("omniauth-oauth2")
 

data/dummy-preauth/.gitignore

@@ -0,0 +1,16 @@
+# See http://help.github.com/ignore-files/ for more about ignoring files.
+#
+# If you find yourself ignoring temporary files generated by your text editor
+# or operating system, you probably want to add a global ignore instead:
+#   git config --global core.excludesfile '~/.gitignore_global'
+
+# Ignore bundler config.
+/.bundle
+
+# Ignore the default SQLite database.
+/db/*.sqlite3
+/db/*.sqlite3-journal
+
+# Ignore all logfiles and tempfiles.
+/log/*.log
+/tmp

data/dummy-preauth/Gemfile

@@ -0,0 +1,42 @@
+source 'https://rubygems.org'
+
+# Bundle edge Rails instead: gem 'rails', github: 'rails/rails'
+gem 'rails', '4.0.0.beta1'
+
+gem 'sqlite3'
+gem 'dailycred', path: '../'
+gem "nifty-generators", :group => :development
+gem 'protected_attributes'
+# Gems used only for assets and not required
+# in production environments by default.
+group :assets do
+  gem 'sass-rails',   '~> 4.0.0.beta1'
+  gem 'coffee-rails', '~> 4.0.0.beta1'
+
+  # See https://github.com/sstephenson/execjs#readme for more supported runtimes
+  # gem 'therubyracer', platforms: :ruby
+
+  gem 'uglifier', '>= 1.0.3'
+end
+
+gem 'jquery-rails'
+
+# Turbolinks makes following links in your web application faster. Read more: https://github.com/rails/turbolinks
+gem 'turbolinks'
+
+# Build JSON APIs with ease. Read more: https://github.com/rails/jbuilder
+gem 'jbuilder', '~> 1.0.1'
+
+# To use ActiveModel has_secure_password
+# gem 'bcrypt-ruby', '~> 3.0.0'
+
+# Use unicorn as the app server
+# gem 'unicorn'
+
+# Deploy with Capistrano
+# gem 'capistrano', group: :development
+
+# To use debugger
+# gem 'debugger'
+
+gem "mocha", group: :test

data/dummy-preauth/README.rdoc

@@ -0,0 +1,28 @@
+== README
+
+This README would normally document whatever steps are necessary to get the
+application up and running.
+
+Things you may want to cover:
+
+* Ruby version
+
+* System dependencies
+
+* Configuration
+
+* Database creation
+
+* Database initialization
+
+* How to run the test suite
+
+* Services (job queues, cache servers, search engines, etc.)
+
+* Deployment instructions
+
+* ...
+
+
+Please feel free to use a different markup language if you do not plan to run
+<tt>rake doc:app</tt>.

data/dummy-preauth/Rakefile

@@ -0,0 +1,6 @@
+# Add your own tasks in files placed in lib/tasks ending in .rake,
+# for example lib/tasks/capistrano.rake, and they will automatically be available to Rake.
+
+require File.expand_path('../config/application', __FILE__)
+
+DummyPreauth::Application.load_tasks

data/dummy-preauth/app/assets/javascripts/application.js

@@ -0,0 +1,16 @@
+// This is a manifest file that'll be compiled into application.js, which will include all the files
+// listed below.
+//
+// Any JavaScript/Coffee file within this directory, lib/assets/javascripts, vendor/assets/javascripts,
+// or vendor/assets/javascripts of plugins, if any, can be referenced here using a relative path.
+//
+// It's not advisable to add code directly here, but if you do, it'll appear at the bottom of the
+// compiled file.
+//
+// WARNING: THE FIRST BLANK LINE MARKS THE END OF WHAT'S TO BE PROCESSED, ANY BLANK LINE SHOULD
+// GO AFTER THE REQUIRES BELOW.
+//
+//= require jquery
+//= require jquery_ujs
+//= require turbolinks
+//= require_tree .

data/{dummy/app/assets/javascripts/posts.js.coffee → dummy-preauth/app/assets/javascripts/welcome.js.coffee}

@@ -1,3 +1,3 @@
 # Place all the behaviors and hooks related to the matching controller here.
 # All this logic will automatically be available in application.js.
-# You can use CoffeeScript in this file: http://jashkenas.github.com/coffee-script/
+# You can use CoffeeScript in this file: http://coffeescript.org/

data/dummy-preauth/app/assets/stylesheets/application.css

@@ -0,0 +1,13 @@
+/*
+ * This is a manifest file that'll be compiled into application.css, which will include all the files
+ * listed below.
+ *
+ * Any CSS and SCSS file within this directory, lib/assets/stylesheets, vendor/assets/stylesheets,
+ * or vendor/assets/stylesheets of plugins, if any, can be referenced here using a relative path.
+ *
+ * You're free to add application-wide styles to this file and they'll appear at the top of the
+ * compiled file, but it's generally better to create a new file per style scope.
+ *
+ *= require_self
+ *= require_tree .
+ */

data/{dummy/app/assets/stylesheets/posts.css.scss → dummy-preauth/app/assets/stylesheets/welcome.css.scss}

@@ -1,3 +1,3 @@
-// Place all the styles related to the posts controller here.
+// Place all the styles related to the welcome controller here.
 // They will automatically be included in application.css.
 // You can use Sass (SCSS) here: http://sass-lang.com/

data/dummy-preauth/app/controllers/application_controller.rb

@@ -0,0 +1,6 @@
+class ApplicationController < ActionController::Base
+  include ControllerAuthentication
+  # Prevent CSRF attacks by raising an exception.
+  # For APIs, you may want to use :null_session instead.
+  protect_from_forgery with: :exception
+end

data/dummy-preauth/app/controllers/sessions_controller.rb

@@ -0,0 +1,34 @@
+class SessionsController < ApplicationController
+  def new
+  end
+
+  def create
+    user = User.authenticate(params[:login], params[:password])
+    if user
+      session[:user_id] = user.id
+      redirect_to_target_or_default root_url, :notice => "Logged in successfully."
+    else
+      flash.now[:alert] = "Invalid login or password."
+      render :action => 'new'
+    end
+  end
+
+  def destroy
+    session[:user_id] = nil
+    redirect_to root_url, :notice => "You have been logged out."
+  end
+
+  def callback
+    auth_hash = request.env['omniauth.auth']
+    if auth_hash['uid']
+      @user = User.find_or_create_by(uuid: auth_hash['uid'])
+      @user.uuid = auth_hash['uid']
+      @user.save
+      session[:user_id] = @user.id
+      flash[:notice] = "Logged in successfully."
+    else
+      flash[:notice] = "There was an error logging you in."
+    end
+    redirect_to_target_or_default root_url
+  end
+end

data/dummy-preauth/app/controllers/users_controller.rb

@@ -0,0 +1,30 @@
+class UsersController < ApplicationController
+  before_filter :login_required, :except => [:new, :create]
+
+  def new
+    @user = User.new
+  end
+
+  def create
+    @user = User.new(params[:user])
+    if @user.save
+      session[:user_id] = @user.id
+      redirect_to root_url, :notice => "Thank you for signing up! You are now logged in."
+    else
+      render :action => 'new'
+    end
+  end
+
+  def edit
+    @user = current_user
+  end
+
+  def update
+    @user = current_user
+    if @user.update_attributes(params[:user])
+      redirect_to root_url, :notice => "Your profile has been updated."
+    else
+      render :action => 'edit'
+    end
+  end
+end