Add sessions_controller for login functionality. Add #new and #create actions with flash error messaging. Add #destroy session action (logout) with no success or error messaging.
Add users_helper with a #current_user helper to find the current_user based on session.
Add sessions (login) routes to routes.rb.
Add 2 'named' routes to make user paths cleaner throughout views. Signup_form and signup are now url/path helpers for users#new and users#create, respectively.
Change incorrect route mapper from 'destroy' to 'delete.'
Add temporary Bcrypt implementation methods before switching over to correct use of Bcrypt within rails > 3.
Add has_secure_password to User model for newer Rails-Bcrypt integration. Remove unneeded Bcrypt User model methods. Change User model validation to check :password_digest instead of :password_hash.
Replace :password_hash with :password_digest as is required by the newer Bcrypt-Rails integration using the HasSecurePassword feature.
Change all occurences of :password_hash to :password_digest within User specs (models and controllers) and User factory.
Migrate local DB, which changes schema to use password_digest.
Comment out sessions_controller methods while testing new user auth implementation for signup. Add a new named route for /signup -- aesthetic reasons.
Remove unneeded #password Bcrypt helper call in user #create action.
Add conditional check for User object creation failure with error messaging and session being set within #create action of UsersController. Change redirects to use path helper methods.
Formatting and whitespace updates.
Add correct has_secure_password implementation of sessions with Rails 4 and the latest Bcrypt gem methods.
Merge pull request #27 from tiger-swallowtails-2014/CF_login_implementation

CF Signup Reimplementation with 'Rails way' of using Bcrypt. Login implementation.
YOLO MERGE - 4 Tests should still be failing. All other functionality is either passing test suite or manually confirmed with self-user testing before merge. Make sure to rebase your local master with this update and then drop your DB and recreate/migrate (because there was bad user data with the old password_hash field -- so glad this isn't the real world!). Don't hate a player.