What do you do if your legacy data defies convention or is just generally complex? Here are some notes from my recent experience using rake to accomplish difficult data migrations.
(December 11, 2011)
Rails developers with deadlines will love ActiveAdmin for building high-quality interfaces for managing a site's data.
(November 11, 2011)
Here's the general process I follow whenever adding authorization—the logic that says what a user's allowed to do—to my Rails applications.
(October 06, 2011)
There's no shortage of approaches to adding password-based security to your Rails applications. Here's a look at the current lineup.
(September 21, 2011)
Get legacy data? Trucker makes moving it from old codebases into new Rails apps with relative ease.
(September 16, 2011)
Get e-mail feedback from your site's visitors though this simple-to-implement web form.
(September 07, 2011)
Let your users opt out of a form and return to the page they came from with this simple helper.
(June 16, 2011)
You don't need to send out e-mail messages to real addresses during development with these two easy-to-use options for SMTP handling.
(May 26, 2011)
Don't forget, RVM gemsets are great for trying out pre-release versions of Rails without interfering with other work. Here's a reminder on how to set that up.
(May 08, 2011)
The very convenient try() method has been available to Rails developers since version 2.3, but it's easy to forget if you're not in the habit of using it. Here's a brief primer.
(April 28, 2011)