Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Commits on Sep 29, 2012
  1. @aripollak @croaky

    Don't expose the existence of a user

    aripollak authored croaky committed
    When a user resets their password, don't expose the existence of
    their email address in the instruction text. This is a security best
    practice:
    
    http://goo.gl/Ayb64
Commits on Sep 20, 2012
  1. @croaky
  2. @croaky
  3. @croaky
  4. @croaky

    Clean up Github links in README

    croaky authored
Commits on Sep 14, 2012
  1. @adarsh

    Update LICENSE copyright years

    adarsh authored
    * Update LICENSE to agree with README.md copyright years
  2. @croaky

    Improve README

    croaky authored
    * Generalize versions of Rails/Ruby we test against.
    * Add `bundle` line.
    * Order main API walkthrough by importance and group authorization.
    * Use Ruby 1.9 hash syntax.
    * Get closer to 80 character limit on lines with links.
    * Use Ruby . or # syntax to evoke class or instance method.
    * Add Code Climate badge.
Commits on Aug 31, 2012
  1. @kdaigle @mike-burns
  2. @kdaigle @mike-burns

    Rescue BCrypt Invalid Hash only in migration strategy

    kdaigle authored mike-burns committed
  3. @mike-burns

    Appraisal droppings

    mike-burns authored
Commits on Aug 20, 2012
  1. @jbgo
Commits on Aug 14, 2012
  1. @gabebw @croaky

    Use a released version of addressable in Gemfile.lock

    gabebw authored croaky committed
    addressable 2.3.1, the version to which the Gemfile was previously
    locked, has been yanked:
    
    https://rubygems.org/gems/addressable/versions
Commits on Jul 23, 2012
  1. @croaky

    Correct NEWS and README

    croaky authored
    * You can use Clearance after you've created a Rails app or users
      table. If you have users already, you'll need to edit the default
      migration that Clearance generates.
    * We are testing against latest Rails 3.0.x, 3.1.x, and 3.2.x.
  2. @gabebw
  3. @mike-burns

    Bump to 1.0.0.rc1

    mike-burns authored
  4. @mike-burns
  5. @mike-burns
  6. @mike-burns

    Clearance cannot be added to an existing app

    mike-burns authored
    Since the generated migration adds non-NULL requirements to columns, and
    since we never add Clearance to existing apps, we cannot trivially test
    the nuances involved in that situation. For now, we do not support this.
Commits on Jul 22, 2012
  1. @croaky

    Upgrade dependencies

    croaky authored
    * Support Rails 3.0.15, 3.1.6, 3.2.6.
    * Apply style guidelines to test suite.
    * Be more strict about development dependencies.
  2. @croaky

    [#204] Remove flash message from users#create

    croaky authored
    * Flash message is redundant to validation error displayed by
      libraries such as dynamic_form, simple_form, or formtastic.
    * We are not bundling one of the form libraries with Clearance
      in order to leave that decision to the developer.
  3. @croaky

    [#206] Improve data integrity

    croaky authored
    By default, we want email, encrypted_password, and remember_token to
    enforce a NOT NULL constraint.
  4. @croaky

    Overhaul README.md

    croaky authored
    Intention is to better communicate the API.
  5. @croaky

    Apply style guidelines

    croaky authored
    * Use single quotes unless interpolating.
    * Do not align tokens.
    * Add a newline between lines of code and blocks.
    * Alphabetize methods and lists of attributes.
    
    Additional refactoring:
    
    * Refactor new_indexes to more appropriately use a Hash.
    * Refactor collections to use Symbol#to_proc to shorten lines.
    * Use consistent naming patterns (existing_*, new_*).
    * Remove `each` naming convention on enumerators.
    * Remove now unnecessary GOALS file.
Commits on Jul 21, 2012
  1. @croaky

    Add Appraisal install line to CONTRIBUTING.md

    croaky authored
    * Setting up Appraisal is necessary to run the test suite.
Commits on Jul 19, 2012
  1. @mike-burns

    Remove the salt from the DB migration

    mike-burns authored
    The salt column is only needed for SHA1 and MD5 strategies, which  are
    not the default. The README contains instructions for adding the salt
    back before switching to those strategies.
Commits on Jun 29, 2012
  1. @mike-burns

    How to hit 1.0.0

    mike-burns authored
  2. @mike-burns

    BCrypt for passwords

    Dan Croak and Gabe Berke-Williams authored mike-burns committed
    This commit makes BCrypt the default for new setups, and introduces a
    strategy for converting existing infrastructure to BCrypt.
    
    To switch to BCrypt now:
    
        Clearance.configure do |config|
          config.password_strategy = Clearance::PasswordStrategies::BCrypt
        end
    
    To set the password strategy to the conversion layer:
    
        Clearance.configure do |config|
          config.password_strategy = Clearance::PasswordStrategies::BCryptMigrationFromSHA1
        end
    
    To continue to use SHA1:
    
        Clearance.configure do |config|
          config.password_strategy = Clearance::PasswordStrategies::SHA1
        end
  3. @mike-burns

    Provide router constraints

    Arun Agrawal and Gabe Berke-Williams authored mike-burns committed
    Adds SignedInConstraint and SignedOutConstraint, useful from the Rails
    router. For example, to redirect admins to their admin dashboard as the
    home page:
    
        constraints(SignedInConstraint.new {|user| user.admin?}) do
          root :to => 'admins/dashboard#index'
        end
Commits on Jun 18, 2012
  1. @gabebw
  2. @gabebw

    Relax bundler dependency.

    gabebw authored
Commits on Jun 13, 2012
  1. @gabebw

    Encourage people to sign up in the flash message

    Arun Agrawal and Gabe Berke-Williams authored gabebw committed
    Fixes #163.
  2. @gabebw

    Remove init.rb.

    gabebw authored
Commits on Jun 7, 2012
  1. @gabebw

    Merge pull request #197 from jsteiner/master

    gabebw authored
    Fix a broken step definition
  2. @jsteiner
Something went wrong with that request. Please try again.