<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Scottie’s Tech.Info &#187; rails</title>
	<atom:link href="http://scottiestech.info/tag/rails/feed/" rel="self" type="application/rss+xml" />
	<link>http://scottiestech.info</link>
	<description>A chimpanzee and two trainees could run her!</description>
	<lastBuildDate>Tue, 24 Jan 2012 18:03:47 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Fixing the Rails 3 Fragment Cache Path</title>
		<link>http://scottiestech.info/2011/07/23/fixing-the-rails-3-fragment-cache-path/</link>
		<comments>http://scottiestech.info/2011/07/23/fixing-the-rails-3-fragment-cache-path/#comments</comments>
		<pubDate>Sat, 23 Jul 2011 11:21:24 +0000</pubDate>
		<dc:creator>Scottie</dc:creator>
				<category><![CDATA[Programming]]></category>
		<category><![CDATA[caching]]></category>
		<category><![CDATA[rails]]></category>
		<category><![CDATA[ruby]]></category>

		<guid isPermaLink="false">http://scottiestech.info/?p=585</guid>
		<description><![CDATA[Let&#8217;s say you were using Rails 2.3.x, and you made the (wise) decision to implement heavy fragment caching. Then let&#8217;s say that you updated to Rails 3.x. At that point, you probably noticed that Rails 3 does something seriously annoying with the paths where it caches fragments. In Rails 2, doing this: Gave you a [...]]]></description>
		<wfw:commentRss>http://scottiestech.info/2011/07/23/fixing-the-rails-3-fragment-cache-path/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>How to Make Your Rails 2.3 App Work with Ruby 1.9</title>
		<link>http://scottiestech.info/2010/12/16/how-to-make-your-rails-2-3-app-work-with-ruby-1-9/</link>
		<comments>http://scottiestech.info/2010/12/16/how-to-make-your-rails-2-3-app-work-with-ruby-1-9/#comments</comments>
		<pubDate>Thu, 16 Dec 2010 12:22:16 +0000</pubDate>
		<dc:creator>Scottie</dc:creator>
				<category><![CDATA[Programming]]></category>
		<category><![CDATA[encoding]]></category>
		<category><![CDATA[rails]]></category>
		<category><![CDATA[ruby]]></category>
		<category><![CDATA[ruby 1.9]]></category>
		<category><![CDATA[utf8]]></category>

		<guid isPermaLink="false">http://scottiestech.info/?p=463</guid>
		<description><![CDATA[If you're like me, you've got a Rails 2.3.x application running on Ruby 1.8.x - or perhaps Ruby Enterprise Edition. Well, that's all fine and dandy, but Ruby 1.9.2 is about twice as fast as even REE 1.8.7. So, you'll probably want to upgrade to the new version of Ruby. Problem is, you upgrade Ruby and then your Rails 2.3 app starts whining about character encoding problems and possibly other stuff. Nobody seems to have written a one-stop guide to upgrading your Rails app to Ruby 1.9... Until now!]]></description>
		<wfw:commentRss>http://scottiestech.info/2010/12/16/how-to-make-your-rails-2-3-app-work-with-ruby-1-9/feed/</wfw:commentRss>
		<slash:comments>9</slash:comments>
		</item>
		<item>
		<title>How to Make Rails and PHP Apps Fully UTF-8 Compliant with MySQL</title>
		<link>http://scottiestech.info/2010/08/07/how-to-make-rails-and-php-apps-fully-utf-8-compliant-with-mysql/</link>
		<comments>http://scottiestech.info/2010/08/07/how-to-make-rails-and-php-apps-fully-utf-8-compliant-with-mysql/#comments</comments>
		<pubDate>Sat, 07 Aug 2010 10:46:50 +0000</pubDate>
		<dc:creator>Scottie</dc:creator>
				<category><![CDATA[Programming]]></category>
		<category><![CDATA[database]]></category>
		<category><![CDATA[mysql]]></category>
		<category><![CDATA[php]]></category>
		<category><![CDATA[rails]]></category>
		<category><![CDATA[utf8]]></category>

		<guid isPermaLink="false">http://scottiestech.info/?p=429</guid>
		<description><![CDATA[Every web programmer knows that UTF-8 is where it's at these days. Even if you are coding something for only the US market, you're still probably going to run into names, addresses, or whatever with accented characters. You've probably run into the situation where you hope into phpMyAdmin and edit some table row, and what to your wondering eyes should appear, but something like this: "Voici un article franÃ§ais." And yet, when you view the web page and edit the content in your app, it looks and works fine! What's going on here?]]></description>
		<wfw:commentRss>http://scottiestech.info/2010/08/07/how-to-make-rails-and-php-apps-fully-utf-8-compliant-with-mysql/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Fixing the &#8220;ActionMailer: Hostname not match server certificate&#8221; Error</title>
		<link>http://scottiestech.info/2009/12/21/fixing-the-actionmailer-hostname-not-match-server-certificate-error/</link>
		<comments>http://scottiestech.info/2009/12/21/fixing-the-actionmailer-hostname-not-match-server-certificate-error/#comments</comments>
		<pubDate>Mon, 21 Dec 2009 16:03:44 +0000</pubDate>
		<dc:creator>Scottie</dc:creator>
				<category><![CDATA[Programming]]></category>
		<category><![CDATA[rails]]></category>
		<category><![CDATA[ruby]]></category>

		<guid isPermaLink="false">http://scottiestech.info/?p=316</guid>
		<description><![CDATA[If you have a Rails app that sends e-mails, you are probably using ActionMailer. Unfortunately, starting with Rails 2.2.2, you may have encountered a wonderfully annoying little error that looks like this:

OpenSSL::SSL::SSLError (hostname was not match with the server certificate)

The are quite a few sites out there that give monkey patches for this problem, but those aren't very useful because the next time you upgrade Rails, the monkey patch gets obliterated and you're back to square 1. And then you have to remember how you monkeyed with the it last time to get it working. Ug... Instead, fix it the right way!]]></description>
		<wfw:commentRss>http://scottiestech.info/2009/12/21/fixing-the-actionmailer-hostname-not-match-server-certificate-error/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>Increase the Performance of Fragment Caching in Rails</title>
		<link>http://scottiestech.info/2009/12/04/increase-the-performance-of-fragment-caching-in-rails/</link>
		<comments>http://scottiestech.info/2009/12/04/increase-the-performance-of-fragment-caching-in-rails/#comments</comments>
		<pubDate>Fri, 04 Dec 2009 15:02:51 +0000</pubDate>
		<dc:creator>Scottie</dc:creator>
				<category><![CDATA[Programming]]></category>
		<category><![CDATA[cache]]></category>
		<category><![CDATA[rails]]></category>
		<category><![CDATA[ruby]]></category>

		<guid isPermaLink="false">http://scottiestech.info/?p=305</guid>
		<description><![CDATA[If you use Rails on a high-traffic site, you know that as your number of users increases, you have three main options:

   1. Add servers to handle the load
   2. Optimize your queries
   3. Improve your caching scheme

You may be surprised to know that most people go for Door #1. It's a lot easier. You don't have to really do tons of work to rewrite your code and actually make it efficient. You don't have to ditch "the Rails Way" and start actually thinking about what the database layer is doing to slow your site down to a crawl. And you don't have to think about how Rails' cache expiry functions actually work. Finally - and best of all - you can just pass the costs on to your customer, right??

Of course, to achieve good performance, you can use things like Phusion Passenger. But that alone ain't gonna cut it. You also have to optimize your queries, stop doing things The Rails Way and start thinking for yourself, and of course optimize your caching scheme.

In this episode, I'm going to tell you one very cool way to turbocharge your caching setup!]]></description>
		<wfw:commentRss>http://scottiestech.info/2009/12/04/increase-the-performance-of-fragment-caching-in-rails/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Rails 2.3: How to Access Custom Columns in the Sessions Table</title>
		<link>http://scottiestech.info/2009/04/02/rails-23-how-to-access-custom-columns-in-the-sessions-table/</link>
		<comments>http://scottiestech.info/2009/04/02/rails-23-how-to-access-custom-columns-in-the-sessions-table/#comments</comments>
		<pubDate>Thu, 02 Apr 2009 17:09:34 +0000</pubDate>
		<dc:creator>Scottie</dc:creator>
				<category><![CDATA[Programming]]></category>
		<category><![CDATA[rails]]></category>
		<category><![CDATA[ruby]]></category>

		<guid isPermaLink="false">http://scottiestech.info/?p=106</guid>
		<description><![CDATA[Say you were using the active_record_store for sessions in Rails 2.2, and you added your own custom column(s) to the default sessions table in your database. You might have done so because you wanted to add, say, the user's id number to each entry in the sessions table. This would let you do things like quickly and efficiently delete a user's session. Unfortunately, when you upgrade to Rails 2.3.2, your session hack will be seriously busted. Here's how to fix it.]]></description>
		<wfw:commentRss>http://scottiestech.info/2009/04/02/rails-23-how-to-access-custom-columns-in-the-sessions-table/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Rails Custom 404 Page: Don&#8217;t Forget the Status Code!</title>
		<link>http://scottiestech.info/2009/03/16/rails-custom-404-page-dont-forget-the-status-code/</link>
		<comments>http://scottiestech.info/2009/03/16/rails-custom-404-page-dont-forget-the-status-code/#comments</comments>
		<pubDate>Sun, 15 Mar 2009 23:46:43 +0000</pubDate>
		<dc:creator>Scottie</dc:creator>
				<category><![CDATA[Programming]]></category>
		<category><![CDATA[rails]]></category>
		<category><![CDATA[ruby]]></category>

		<guid isPermaLink="false">http://scottiestech.info/?p=85</guid>
		<description><![CDATA[<a title="Ruby on Rails" href="http://rubyonrails.org/" target="_blank">Ruby on Rails</a> has become a rather popular framework that many have used to easily and quickly create some pretty powerful web sites. As with any web programming language or framework, it certainly does have its problems. A lot of people get their Rails coding tips and tricks from others - basically what you're doing right now! The solutions you find online aren't always optimal, and are sometimes downright scary.

Take a custom 404 error page. It's easy enough to make, but you have to be careful about how you actually implement it.]]></description>
		<wfw:commentRss>http://scottiestech.info/2009/03/16/rails-custom-404-page-dont-forget-the-status-code/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

