ubiquitous_user 0.3.0 → 0.3.1

data/README.rdoc

@@ -15,41 +15,34 @@ user = userObject.
 This library also provides an authorize method, to use as a filter for those
 actions that really require a logged in user.
 
-An important consideration is that users should be mergeable now. If you have
-a user with an account, and that user comes back a month latter, he may start
-to operate your site with the new ghost account and only log in latter on. At
-that moment you should merge the accounts.
+The user model and how to authenticate is your responsibility; ubiquity_user
+doesn't try solve those problem (not yet at least). I may recommend
+{rails_openid}[http://github.com/pupeno/rails_openid] for authentication, but
+maybe it's only because I wrote it.
+
+Since people just accessing your web site will have a user, people that is
+already registered at your web site may have an anonymous user with activity in
+it. You should try to merge it.
 
 == Installation
 
-This gem is provided through Gemcutter so you need to have gem configured to
-pull gems from Gemcutter.
+This gem is provided through RubyGems.org so you need to have gem configured to
+pull gems from RubyGems.org.
 
-=== Enabling Gemcutter
+=== Enabling RubyGems.org (formerly known as GemCutter)
 
-A properly configured environment would be like this:
+You can skip this if you have RubyGems.org enabled (which is going to be the
+default in the future anyway). A properly configured environment should list
+rubygems.org or gemcutter.org in the gem sources, like:
 
   $ gem sources
   *** CURRENT SOURCES ***
-  
-  http://gemcutter.org
-  http://gems.rubyforge.org/
-  http://gems.github.com
-
-If you don't have http://gemcutter.org in your sources then you need to add. I
-know two ways to do. One is installing Gemcutter and running gem tumble:
 
-  $ sudo gem install gemcutter
-  $ gem tumble
+  http://rubygems.org/
 
-Be careful that gem tumble will remove Gemcutter from your repositories if it's
-already there.
+If you don't have it, you can probably add it this way:
 
-The other way is by hand like this:
-
-  $ gem source -a http://gemcutter.org
-
-I'm not sure if there's any difference. I think there isn't one.
+  $ gem source -a http://rubygems.org/
 
 === Installing ubiquitous_user manually
 
@@ -59,7 +52,21 @@ It's simple a matter of running:
 
 and that's it. Let me know if something breaks.
 
-=== Installing through your Ruby on Rails project
+=== Installing through your Ruby on Rails 3 project
+
+In the +Gemfile+ file of your Ruby on Rails project you'll need to add:
+
+  gem "ubiquitous_user"
+
+after that run
+
+  bundle install
+
+and watch the magic happen, all required gems will be installed. Configuring
+your Rails project like that is something you'll need anyway, so this is my
+recommended way.
+
+=== Installing through your Ruby on Rails 2.3 project
 
 In the +environment.rb+ file of your Ruby on Rails project you'll have some
 commented out lines like this:
@@ -120,7 +127,7 @@ You can use user= and authorize in the controllers, for example:
   end
 
 Another interesting method is the authorize generator, which allows you to
-specify the message you want to give the authorization is not granted. For
+specify the message you want to give when the authorization is not granted. For
 example:
 
   class ProfilesController < ApplicationController

data/Rakefile

@@ -1,3 +1,6 @@
+# coding: utf-8
+# Copyright 2010 J. Pablo Fernández
+
 require 'rubygems'
 require 'rake'
 

data/VERSION

@@ -1 +1 @@
-0.3.0
+0.3.1

data/lib/ubiquitous_user.rb

@@ -1,3 +1,6 @@
+# coding: utf-8
+# Copyright 2010 J. Pablo Fernández
+
 module UsableConfig
   @user_model = :User
   @user_model_new = :new

data/test/helper.rb

@@ -1,8 +1,10 @@
+# coding: utf-8
+# Copyright 2010 J. Pablo Fernández
+
 require 'rubygems'
 require 'test/unit'
 require 'shoulda'
 require 'mocha'
-require 'ruby-debug'
 
 $LOAD_PATH.unshift(File.join(File.dirname(__FILE__), '..', 'lib'))
 $LOAD_PATH.unshift(File.dirname(__FILE__))

data/test/test_ubiquitous_user.rb

@@ -1,3 +1,6 @@
+# coding: utf-8
+# Copyright 2010 J. Pablo Fernández
+
 require 'helper'
 
 class TestUbiquitousUser < Test::Unit::TestCase

metadata

@@ -1,7 +1,12 @@
 --- !ruby/object:Gem::Specification 
 name: ubiquitous_user
 version: !ruby/object:Gem::Version 
-  version: 0.3.0
+  prerelease: false
+  segments: 
+  - 0
+  - 3
+  - 1
+  version: 0.3.1
 platform: ruby
 authors: 
 - "J. Pablo Fern\xC3\xA1ndez"
@@ -9,19 +14,23 @@ autorequire:
 bindir: bin
 cert_chain: []
 
-date: 2009-12-26 00:00:00 +01:00
+date: 2010-03-07 00:00:00 +01:00
 default_executable: 
 dependencies: 
 - !ruby/object:Gem::Dependency 
   name: actionpack
-  type: :runtime
-  version_requirement: 
-  version_requirements: !ruby/object:Gem::Requirement 
+  prerelease: false
+  requirement: &id001 !ruby/object:Gem::Requirement 
     requirements: 
     - - ">="
       - !ruby/object:Gem::Version 
+        segments: 
+        - 2
+        - 0
+        - 0
         version: 2.0.0
-    version: 
+  type: :runtime
+  version_requirements: *id001
 description: Create accounts for users right away, even when they are anonymous.
 email: pupeno@pupeno.com
 executables: []
@@ -53,18 +62,20 @@ required_ruby_version: !ruby/object:Gem::Requirement
   requirements: 
   - - ">="
     - !ruby/object:Gem::Version 
+      segments: 
+      - 0
       version: "0"
-  version: 
 required_rubygems_version: !ruby/object:Gem::Requirement 
   requirements: 
   - - ">="
     - !ruby/object:Gem::Version 
+      segments: 
+      - 0
       version: "0"
-  version: 
 requirements: []
 
 rubyforge_project: 
-rubygems_version: 1.3.5
+rubygems_version: 1.3.6
 signing_key: 
 specification_version: 3
 summary: Helpers to get and retrieve users ubiquitously