When developing a program in Ruby, you may sometimes encounter a memory leak. For a while now, Ruby has a facility to gather information about what objects are laying around: ObjectSpace.
There are several approaches one can take to debug a leak. This discusses a time-based approach, where a full memory dump is generated every, say, 5 minutes, during a time that the memory leak is showing up. Afterwards, one can look at all the objects, and find out which ones are staying around, causing the
| " ============================================================================= | |
| " Miller Medeiros .vimrc file | |
| " ----------------------------------------------------------------------------- | |
| " heavily inspired by: @factorylabs, @scrooloose, @nvie, @gf3, @bit-theory. | |
| " ============================================================================= | |
| " ----------------------------------------------------------------------------- | |
| " BEHAVIOR | |
| " ----------------------------------------------------------------------------- |
#Simple Authentication with Bcrypt
This tutorial is for adding authentication to a vanilla Ruby on Rails app using Bcrypt and has_secure_password.
The steps below are based on Ryan Bates's approach from Railscast #250 Authentication from Scratch (revised).
You can see the final source code here: repo. I began with a stock rails app using rails new gif_vault
##Steps