password_resetter 1.0.0

data/MIT-LICENSE

@@ -0,0 +1,20 @@
+Copyright 2012 Elias Fatsi
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/README.rdoc

@@ -0,0 +1,3 @@
+= PasswordResetter
+
+This project rocks and uses MIT-LICENSE.

data/Rakefile

@@ -0,0 +1,36 @@
+#!/usr/bin/env rake
+begin
+  require 'bundler/setup'
+rescue LoadError
+  puts 'You must `gem install bundler` and `bundle install` to run rake tasks'
+end
+begin
+  require 'rdoc/task'
+rescue LoadError
+  require 'rdoc/rdoc'
+  require 'rake/rdoctask'
+  RDoc::Task = Rake::RDocTask
+end
+
+RDoc::Task.new(:rdoc) do |rdoc|
+  rdoc.rdoc_dir = 'rdoc'
+  rdoc.title    = 'PasswordResetter'
+  rdoc.options << '--line-numbers'
+  rdoc.rdoc_files.include('README.rdoc')
+  rdoc.rdoc_files.include('lib/**/*.rb')
+end
+
+APP_RAKEFILE = File.expand_path("../spec/dummy/Rakefile", __FILE__)
+load 'rails/tasks/engine.rake'
+
+
+
+Bundler::GemHelper.install_tasks
+
+require 'rspec/core'
+require 'rspec/core/rake_task'
+
+desc "Run all specs in spec directory (excluding plugin specs)"
+RSpec::Core::RakeTask.new(:spec)
+
+task :default => :spec

data/app/assets/javascripts/password_resets.js

@@ -0,0 +1,2 @@
+// Place all the behaviors and hooks related to the matching controller here.
+// All this logic will automatically be available in application.js.

data/app/assets/stylesheets/password_resets.css

@@ -0,0 +1,4 @@
+/*
+  Place all the styles related to the matching controller here.
+  They will automatically be included in application.css.
+*/

data/app/controllers/password_resets_controller.rb

@@ -0,0 +1,37 @@
+class PasswordResetsController < ApplicationController
+  
+  
+  def new
+    @password_reset = PasswordReset.new
+  end                              
+                                   
+  def create                       
+    @password_reset = PasswordReset.new(params[:password_reset])
+    if @password_reset.match_email? && @password_reset.save
+      @password_reset.delete_existing
+      @password_reset.send_password_reset
+      redirect_to root_url, :notice => "Email sent with password reset instructions."
+    else
+      redirect_to new_password_reset_path, :alert => "Could not find a user to match :("
+    end
+  end
+
+  def edit
+    @password_reset = PasswordReset.find_by_reset_token(params[:id])
+    if @password_reset.expired?
+      redirect_to new_password_reset_path, :alert => "Password reset has expired"
+    end
+  end
+
+  def update
+    @password_reset = PasswordReset.find(params[:id])
+    if @password_reset.update_user_password(params[:password_reset][:password], params[:password_reset][:password_confirmation])
+      session[:user_id] = @password_reset.user.id
+      @password_reset.destroy
+      redirect_to root_url, :notice => "Password has been reset, hurray!"
+    else
+      render :edit
+    end
+  end
+  
+end

data/app/helpers/password_resets_helper.rb

@@ -0,0 +1,2 @@
+module PasswordResetsHelper
+end

data/app/mailers/password_reset_mailer.rb

@@ -0,0 +1,9 @@
+class PasswordResetMailer < ActionMailer::Base
+  default from: "haxxor_news@example.com"
+
+  def password_reset(user, password_reset)
+    @user = user
+    @token = password_reset.reset_token
+    mail :to => user.email, :subject => "Password Reset"
+  end
+end

data/app/models/password_reset.rb

@@ -0,0 +1,57 @@
+class PasswordReset < ActiveRecord::Base
+  
+  belongs_to :user
+  
+  attr_accessible :user, :email, :password, :password_confirmation, :reset_token, :reset_sent_at
+  
+  validates_presence_of :email
+    
+  def match_email?
+    guest = User.where(['email = ?', email]).first      
+    if guest.present?
+      self.update_attributes(:user => guest)
+    else
+      false
+    end
+  end
+
+  def send_password_reset
+    generate_token
+    self.update_attributes(:reset_sent_at => Time.zone.now)
+    save
+    PasswordResetMailer.password_reset(user, self).deliver
+  end
+  
+  def update_user_password(password, confirmation)
+    if passwords_valid?(password, confirmation)
+      user.password = password
+      user.password_confirmation = confirmation
+      user.save
+    else
+      false
+    end
+  end
+  
+  def expired?
+    reset_sent_at < 2.hours.ago
+  end
+
+  def delete_existing
+    PasswordReset.all.each do |pr|
+      pr.delete if (pr.user_id == user.id) && (pr != self)
+    end
+  end
+  
+  private
+  def generate_token
+    begin
+      self.reset_token = SecureRandom.urlsafe_base64
+    end  while PasswordReset.exists?(:reset_token => self.reset_token)
+    self.save
+  end
+  
+  def passwords_valid?(password, confirmation)
+    password.present? && confirmation.present? && password == confirmation 
+  end
+  
+end

data/app/views/password_reset_mailer/password_reset.text.erb

@@ -0,0 +1,7 @@
+To reset your password, click the URL below.
+
+<%= edit_password_reset_url(@token) %>
+
+If you did not request your password to be reset, just ignore this email and your password will continue to stay the same.
+
+

data/app/views/password_resets/edit.html.erb

@@ -0,0 +1,7 @@
+<%= simple_form_for @password_reset do |f| %>
+  <div class="field">
+    <%= f.input :password, :class => "password-reset-input password" %>
+    <%= f.input :password_confirmation, :class => "password-reset-input password-confirmation" %>
+  </div>
+  <div class="actions"><%= f.submit "Update Password", :class => "password-reset-button update" %></div>
+<% end %>

data/app/views/password_resets/new.html.erb

@@ -0,0 +1,9 @@
+<div class="password-reset-text reset"> Please enter your email address to reset your password.</div>
+
+<%= simple_form_for @password_reset do |f| %>
+  <%= f.full_error :user %>
+  <div class="field">
+    <%= f.input :email, :label => "Enter your Email Address", :class => "password-reset-input email" %>
+  </div>
+  <div class="actions"><%= submit_tag "Reset Password", :class => "password-reset-button reset" %></div>
+<% end %>

data/bin/execute_migrations

@@ -0,0 +1,5 @@
+#!/usr/bin/env ruby
+
+require 'password_resetter'
+rake password_resetter_engine:install:migrations
+rake db:migrate

data/config/routes.rb

@@ -0,0 +1,5 @@
+Rails.application.routes.draw do
+  
+  resources :password_resets
+  
+end

data/db/migrate/20120829163145_create_password_resets.rb

@@ -0,0 +1,14 @@
+class CreatePasswordResets < ActiveRecord::Migration
+  def change
+    create_table :password_resets do |t|
+      t.string :email
+      t.string :password
+      t.string :password_confirmation
+      t.string :reset_token
+      t.datetime :reset_sent_at
+      t.integer :user_id
+      
+      t.timestamps
+    end
+  end
+end

data/lib/password_resetter.rb

@@ -0,0 +1,4 @@
+require "password_resetter/engine"
+
+module PasswordResetter
+end

data/lib/password_resetter/engine.rb

@@ -0,0 +1,4 @@
+module PasswordResetter
+  class Engine < ::Rails::Engine
+  end
+end

data/lib/password_resetter/version.rb

@@ -0,0 +1,3 @@
+module PasswordResetter
+  VERSION = "1.0.0"
+end

data/lib/tasks/password_resetter_tasks.rake

@@ -0,0 +1,4 @@
+# desc "Explaining what the task does"
+# task :password_resetter do
+#   # Task goes here
+# end

data/spec/dummy/README.rdoc

@@ -0,0 +1,261 @@
+== Welcome to Rails
+
+Rails is a web-application framework that includes everything needed to create
+database-backed web applications according to the Model-View-Control pattern.
+
+This pattern splits the view (also called the presentation) into "dumb"
+templates that are primarily responsible for inserting pre-built data in between
+HTML tags. The model contains the "smart" domain objects (such as Account,
+Product, Person, Post) that holds all the business logic and knows how to
+persist themselves to a database. The controller handles the incoming requests
+(such as Save New Account, Update Product, Show Post) by manipulating the model
+and directing data to the view.
+
+In Rails, the model is handled by what's called an object-relational mapping
+layer entitled Active Record. This layer allows you to present the data from
+database rows as objects and embellish these data objects with business logic
+methods. You can read more about Active Record in
+link:files/vendor/rails/activerecord/README.html.
+
+The controller and view are handled by the Action Pack, which handles both
+layers by its two parts: Action View and Action Controller. These two layers
+are bundled in a single package due to their heavy interdependence. This is
+unlike the relationship between the Active Record and Action Pack that is much
+more separate. Each of these packages can be used independently outside of
+Rails. You can read more about Action Pack in
+link:files/vendor/rails/actionpack/README.html.
+
+
+== Getting Started
+
+1. At the command prompt, create a new Rails application:
+       <tt>rails new myapp</tt> (where <tt>myapp</tt> is the application name)
+
+2. Change directory to <tt>myapp</tt> and start the web server:
+       <tt>cd myapp; rails server</tt> (run with --help for options)
+
+3. Go to http://localhost:3000/ and you'll see:
+       "Welcome aboard: You're riding Ruby on Rails!"
+
+4. Follow the guidelines to start developing your application. You can find
+the following resources handy:
+
+* The Getting Started Guide: http://guides.rubyonrails.org/getting_started.html
+* Ruby on Rails Tutorial Book: http://www.railstutorial.org/
+
+
+== Debugging Rails
+
+Sometimes your application goes wrong. Fortunately there are a lot of tools that
+will help you debug it and get it back on the rails.
+
+First area to check is the application log files. Have "tail -f" commands
+running on the server.log and development.log. Rails will automatically display
+debugging and runtime information to these files. Debugging info will also be
+shown in the browser on requests from 127.0.0.1.
+
+You can also log your own messages directly into the log file from your code
+using the Ruby logger class from inside your controllers. Example:
+
+  class WeblogController < ActionController::Base
+    def destroy
+      @weblog = Weblog.find(params[:id])
+      @weblog.destroy
+      logger.info("#{Time.now} Destroyed Weblog ID ##{@weblog.id}!")
+    end
+  end
+
+The result will be a message in your log file along the lines of:
+
+  Mon Oct 08 14:22:29 +1000 2007 Destroyed Weblog ID #1!
+
+More information on how to use the logger is at http://www.ruby-doc.org/core/
+
+Also, Ruby documentation can be found at http://www.ruby-lang.org/. There are
+several books available online as well:
+
+* Programming Ruby: http://www.ruby-doc.org/docs/ProgrammingRuby/ (Pickaxe)
+* Learn to Program: http://pine.fm/LearnToProgram/ (a beginners guide)
+
+These two books will bring you up to speed on the Ruby language and also on
+programming in general.
+
+
+== Debugger
+
+Debugger support is available through the debugger command when you start your
+Mongrel or WEBrick server with --debugger. This means that you can break out of
+execution at any point in the code, investigate and change the model, and then,
+resume execution! You need to install ruby-debug to run the server in debugging
+mode. With gems, use <tt>sudo gem install ruby-debug</tt>. Example:
+
+  class WeblogController < ActionController::Base
+    def index
+      @posts = Post.all
+      debugger
+    end
+  end
+
+So the controller will accept the action, run the first line, then present you
+with a IRB prompt in the server window. Here you can do things like:
+
+  >> @posts.inspect
+  => "[#<Post:0x14a6be8
+          @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>,
+       #<Post:0x14a6620
+          @attributes={"title"=>"Rails", "body"=>"Only ten..", "id"=>"2"}>]"
+  >> @posts.first.title = "hello from a debugger"
+  => "hello from a debugger"
+
+...and even better, you can examine how your runtime objects actually work:
+
+  >> f = @posts.first
+  => #<Post:0x13630c4 @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>
+  >> f.
+  Display all 152 possibilities? (y or n)
+
+Finally, when you're ready to resume execution, you can enter "cont".
+
+
+== Console
+
+The console is a Ruby shell, which allows you to interact with your
+application's domain model. Here you'll have all parts of the application
+configured, just like it is when the application is running. You can inspect
+domain models, change values, and save to the database. Starting the script
+without arguments will launch it in the development environment.
+
+To start the console, run <tt>rails console</tt> from the application
+directory.
+
+Options:
+
+* Passing the <tt>-s, --sandbox</tt> argument will rollback any modifications
+  made to the database.
+* Passing an environment name as an argument will load the corresponding
+  environment. Example: <tt>rails console production</tt>.
+
+To reload your controllers and models after launching the console run
+<tt>reload!</tt>
+
+More information about irb can be found at:
+link:http://www.rubycentral.org/pickaxe/irb.html
+
+
+== dbconsole
+
+You can go to the command line of your database directly through <tt>rails
+dbconsole</tt>. You would be connected to the database with the credentials
+defined in database.yml. Starting the script without arguments will connect you
+to the development database. Passing an argument will connect you to a different
+database, like <tt>rails dbconsole production</tt>. Currently works for MySQL,
+PostgreSQL and SQLite 3.
+
+== Description of Contents
+
+The default directory structure of a generated Ruby on Rails application:
+
+  |-- app
+  |   |-- assets
+  |       |-- images
+  |       |-- javascripts
+  |       `-- stylesheets
+  |   |-- controllers
+  |   |-- helpers
+  |   |-- mailers
+  |   |-- models
+  |   `-- views
+  |       `-- layouts
+  |-- config
+  |   |-- environments
+  |   |-- initializers
+  |   `-- locales
+  |-- db
+  |-- doc
+  |-- lib
+  |   `-- tasks
+  |-- log
+  |-- public
+  |-- script
+  |-- test
+  |   |-- fixtures
+  |   |-- functional
+  |   |-- integration
+  |   |-- performance
+  |   `-- unit
+  |-- tmp
+  |   |-- cache
+  |   |-- pids
+  |   |-- sessions
+  |   `-- sockets
+  `-- vendor
+      |-- assets
+          `-- stylesheets
+      `-- plugins
+
+app
+  Holds all the code that's specific to this particular application.
+
+app/assets
+  Contains subdirectories for images, stylesheets, and JavaScript files.
+
+app/controllers
+  Holds controllers that should be named like weblogs_controller.rb for
+  automated URL mapping. All controllers should descend from
+  ApplicationController which itself descends from ActionController::Base.
+
+app/models
+  Holds models that should be named like post.rb. Models descend from
+  ActiveRecord::Base by default.
+
+app/views
+  Holds the template files for the view that should be named like
+  weblogs/index.html.erb for the WeblogsController#index action. All views use
+  eRuby syntax by default.
+
+app/views/layouts
+  Holds the template files for layouts to be used with views. This models the
+  common header/footer method of wrapping views. In your views, define a layout
+  using the <tt>layout :default</tt> and create a file named default.html.erb.
+  Inside default.html.erb, call <% yield %> to render the view using this
+  layout.
+
+app/helpers
+  Holds view helpers that should be named like weblogs_helper.rb. These are
+  generated for you automatically when using generators for controllers.
+  Helpers can be used to wrap functionality for your views into methods.
+
+config
+  Configuration files for the Rails environment, the routing map, the database,
+  and other dependencies.
+
+db
+  Contains the database schema in schema.rb. db/migrate contains all the
+  sequence of Migrations for your schema.
+
+doc
+  This directory is where your application documentation will be stored when
+  generated using <tt>rake doc:app</tt>
+
+lib
+  Application specific libraries. Basically, any kind of custom code that
+  doesn't belong under controllers, models, or helpers. This directory is in
+  the load path.
+
+public
+  The directory available for the web server. Also contains the dispatchers and the
+  default HTML files. This should be set as the DOCUMENT_ROOT of your web
+  server.
+
+script
+  Helper scripts for automation and generation.
+
+test
+  Unit and functional tests along with fixtures. When using the rails generate
+  command, template test files will be generated for you and placed in this
+  directory.
+
+vendor
+  External libraries that the application depends on. Also includes the plugins
+  subdirectory. If the app has frozen rails, those gems also go here, under
+  vendor/rails/. This directory is in the load path.