<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/atom10full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><feed xmlns="http://www.w3.org/2005/Atom">
 
 <title>Everyday Rails</title>
 
 <link href="http://everydayrails.com/" />
 <updated>2012-01-24T05:43:47-06:00</updated>
 <id>http://everydayrails.com/</id>
 <author>
   <name>Aaron Sumner</name>
   <email>aaron@everydayrails.com</email>
 </author>
 
 
 <atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/atom+xml" href="http://feeds.feedburner.com/EverydayRails" /><feedburner:info xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" uri="everydayrails" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><link rel="license" type="text/html" href="http://creativecommons.org/licenses/by-nc-sa/3.0/" /><feedburner:emailServiceId xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">EverydayRails</feedburner:emailServiceId><feedburner:feedburnerHostname xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">http://feedburner.google.com</feedburner:feedburnerHostname><entry>
   <title>More advice on legacy data migration in Rails</title>
   <link href="http://everydayrails.com/2011/12/11/legacy-data-migrations-rails.html" />
   <updated>2011-12-11T00:00:00-06:00</updated>
   <id>http://www.everydayrails.com/2011/12/11/legacy-data-migrations-rails</id>
   <content type="html">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.&lt;img src="http://feeds.feedburner.com/~r/EverydayRails/~4/aK-XmlvGxnw" height="1" width="1"/&gt;</content>
 </entry>
 
 <entry>
   <title>How I've been developing an administrative backend with ActiveAdmin</title>
   <link href="http://everydayrails.com/2011/11/11/active-admin.html" />
   <updated>2011-11-11T00:00:00-06:00</updated>
   <id>http://www.everydayrails.com/2011/11/11/active-admin</id>
   <content type="html">Rails developers with deadlines will love ActiveAdmin for building high-quality interfaces for managing a site's data.&lt;img src="http://feeds.feedburner.com/~r/EverydayRails/~4/PISVthFdPEo" height="1" width="1"/&gt;</content>
 </entry>
 
 <entry>
   <title>Authorization advice for Rails 3 and beyond</title>
   <link href="http://everydayrails.com/2011/10/06/rails-authorization.html" />
   <updated>2011-10-06T00:00:00-05:00</updated>
   <id>http://www.everydayrails.com/2011/10/06/rails-authorization</id>
   <content type="html">Here's the general process I follow whenever adding authorization&amp;mdash;the logic that says what a user's allowed to do&amp;mdash;to my Rails applications.&lt;img src="http://feeds.feedburner.com/~r/EverydayRails/~4/eQefR9veTMY" height="1" width="1"/&gt;</content>
 </entry>
 
 <entry>
   <title>Rails authentication today: Options for 3.0 and 3.1</title>
   <link href="http://everydayrails.com/2011/09/21/rails-authentication.html" />
   <updated>2011-09-21T00:00:00-05:00</updated>
   <id>http://www.everydayrails.com/2011/09/21/rails-authentication</id>
   <content type="html">There's no shortage of approaches to adding password-based security to your Rails applications. Here's a look at the current lineup.&lt;img src="http://feeds.feedburner.com/~r/EverydayRails/~4/g-bnlvYYA90" height="1" width="1"/&gt;</content>
 </entry>
 
 <entry>
   <title>Migrate data to Rails applications with Trucker</title>
   <link href="http://everydayrails.com/2011/09/16/rails-legacy-data-migration-trucker.html" />
   <updated>2011-09-16T00:00:00-05:00</updated>
   <id>http://www.everydayrails.com/2011/09/16/rails-legacy-data-migration-trucker</id>
   <content type="html">Get legacy data? Trucker makes moving it from old codebases into new Rails apps with relative ease.&lt;img src="http://feeds.feedburner.com/~r/EverydayRails/~4/MyU5ztIl7ew" height="1" width="1"/&gt;</content>
 </entry>
 
 <entry>
   <title>MailForm: Easy e-mail contact forms for your Rails apps</title>
   <link href="http://everydayrails.com/2011/09/07/rails-contact-form.html" />
   <updated>2011-09-07T00:00:00-05:00</updated>
   <id>http://www.everydayrails.com/2011/09/07/rails-contact-form</id>
   <content type="html">Get e-mail feedback from your site's visitors though this simple-to-implement web form.&lt;img src="http://feeds.feedburner.com/~r/EverydayRails/~4/xgFjUA96jWQ" height="1" width="1"/&gt;</content>
 </entry>
 
 <entry>
   <title>Simple, user-friendly cancel links for your Rails forms</title>
   <link href="http://everydayrails.com/2011/06/16/rails-form-cancel-links.html" />
   <updated>2011-06-16T00:00:00-05:00</updated>
   <id>http://www.everydayrails.com/2011/06/16/rails-form-cancel-links</id>
   <content type="html">Let your users opt out of a form and return to the page they came from with this simple helper.&lt;img src="http://feeds.feedburner.com/~r/EverydayRails/~4/hThLqqV0Whg" height="1" width="1"/&gt;</content>
 </entry>
 
 <entry>
   <title>Better SMTP handling in Rails application development</title>
   <link href="http://everydayrails.com/2011/05/26/rails-smtp-development.html" />
   <updated>2011-05-26T00:00:00-05:00</updated>
   <id>http://www.everydayrails.com/2011/05/26/rails-smtp-development</id>
   <content type="html">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.&lt;img src="http://feeds.feedburner.com/~r/EverydayRails/~4/Bcq-vpdchHU" height="1" width="1"/&gt;</content>
 </entry>
 
 <entry>
   <title>Install Rails 3.1 beta with RVM gemsets (a public service announcement)</title>
   <link href="http://everydayrails.com/2011/05/08/rails-3.1-beta-rvm.html" />
   <updated>2011-05-08T00:00:00-05:00</updated>
   <id>http://www.everydayrails.com/2011/05/08/rails-3.1-beta-rvm</id>
   <content type="html">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.&lt;img src="http://feeds.feedburner.com/~r/EverydayRails/~4/0hq76KENopw" height="1" width="1"/&gt;</content>
 </entry>
 
 <entry>
   <title>try(), try() again in Rails</title>
   <link href="http://everydayrails.com/2011/04/28/rails-try-method.html" />
   <updated>2011-04-28T00:00:00-05:00</updated>
   <id>http://www.everydayrails.com/2011/04/28/rails-try-method</id>
   <content type="html">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.&lt;img src="http://feeds.feedburner.com/~r/EverydayRails/~4/8-YKsKWew-Y" height="1" width="1"/&gt;</content>
 </entry>
 
 
</feed>

