<?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>ClearCove &#187; Ruby/Rails</title>
	<atom:link href="http://clearcove.ca/blog/category/blog/software/rubyrails/feed/" rel="self" type="application/rss+xml" />
	<link>http://clearcove.ca</link>
	<description>Jo Hund's software engineering blog</description>
	<lastBuildDate>Fri, 28 May 2010 16:28:42 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Recipe: Detect whether cookies are enabled in rails</title>
		<link>http://clearcove.ca/blog/2009/09/rails-cookie-detection/</link>
		<comments>http://clearcove.ca/blog/2009/09/rails-cookie-detection/#comments</comments>
		<pubDate>Wed, 30 Sep 2009 03:18:44 +0000</pubDate>
		<dc:creator>Jo Hund</dc:creator>
				<category><![CDATA[Ruby/Rails]]></category>

		<guid isPermaLink="false">http://clearcove.ca/?p=407</guid>
		<description><![CDATA[If your Rails app requires cookies, this recipe is for you: It detects whether cookies are enabled, and if not, shows a message to your users.
 
This recipe checks for the presence of a specific cookie (&#8220;cookie_test&#8221;). If it is present, the request continues normally. If it is not present, then it sets the cookie, [...]]]></description>
		<wfw:commentRss>http://clearcove.ca/blog/2009/09/rails-cookie-detection/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Simplest way to use cron with Rails</title>
		<link>http://clearcove.ca/blog/2009/03/simplest-way-to-use-cron-with-rails/</link>
		<comments>http://clearcove.ca/blog/2009/03/simplest-way-to-use-cron-with-rails/#comments</comments>
		<pubDate>Tue, 31 Mar 2009 04:07:21 +0000</pubDate>
		<dc:creator>Jo Hund</dc:creator>
				<category><![CDATA[Note to self]]></category>
		<category><![CDATA[Ruby/Rails]]></category>
		<category><![CDATA[broadcast]]></category>

		<guid isPermaLink="false">http://clearcove.ca/?p=378</guid>
		<description><![CDATA[For simple applications I use cron to run automated background jobs like sending emails or indexing sphinx.
I like to have all aspects of my application under version control. Cron is no exception. To do this, I add a file named &#8220;crontab&#8221; in /config. In there I add all my cron jobs in regular cron notation.

Then [...]]]></description>
		<wfw:commentRss>http://clearcove.ca/blog/2009/03/simplest-way-to-use-cron-with-rails/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Recipe: RESTful search for Rails</title>
		<link>http://clearcove.ca/blog/2008/12/recipe-restful-search-for-rails/</link>
		<comments>http://clearcove.ca/blog/2008/12/recipe-restful-search-for-rails/#comments</comments>
		<pubDate>Sun, 14 Dec 2008 23:14:33 +0000</pubDate>
		<dc:creator>Jo Hund</dc:creator>
				<category><![CDATA[Ruby/Rails]]></category>
		<category><![CDATA[broadcast]]></category>

		<guid isPermaLink="false">http://clearcove.ca/?p=218</guid>
		<description><![CDATA[This recipe shows you how to search, filter, and sort your resource lists in a restful way. We will look at the most simple way to accomplish this and then provide some pointers to further improvements. This recipe works great with will_paginate. It is an end to end solution (model, view, and controller). This recipe [...]]]></description>
		<wfw:commentRss>http://clearcove.ca/blog/2008/12/recipe-restful-search-for-rails/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>Recipe: Make request environment available to models in Rails</title>
		<link>http://clearcove.ca/blog/2008/08/recipe-make-request-environment-available-to-models-in-rails/</link>
		<comments>http://clearcove.ca/blog/2008/08/recipe-make-request-environment-available-to-models-in-rails/#comments</comments>
		<pubDate>Sun, 31 Aug 2008 19:50:41 +0000</pubDate>
		<dc:creator>Jo Hund</dc:creator>
				<category><![CDATA[Ruby/Rails]]></category>
		<category><![CDATA[broadcast]]></category>

		<guid isPermaLink="false">http://clearcove.ca/?p=273</guid>
		<description><![CDATA[How often do you wish you had access to current_user in one of your models? I needed it for an app that required auditing. I had ActiveRecord call backs on the audited models to create audit entries on every record operation. The problem was that the models had no access to the currently logged in [...]]]></description>
		<wfw:commentRss>http://clearcove.ca/blog/2008/08/recipe-make-request-environment-available-to-models-in-rails/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>Recipe: RESTful permissions for Rails</title>
		<link>http://clearcove.ca/blog/2008/08/recipe-restful-permissions-for-rails/</link>
		<comments>http://clearcove.ca/blog/2008/08/recipe-restful-permissions-for-rails/#comments</comments>
		<pubDate>Sun, 24 Aug 2008 20:59:23 +0000</pubDate>
		<dc:creator>Jo Hund</dc:creator>
				<category><![CDATA[Ruby/Rails]]></category>
		<category><![CDATA[broadcast]]></category>

		<guid isPermaLink="false">http://clearcove.ca/?p=117</guid>
		<description><![CDATA[A common requirement for Rails applications is to check permissions for certain actions on your RESTful application&#8217;s resources. There are many ways to solve this problem, ranging from simple boolean flags to full fledged role based access control. I have tried a lot of approaches and have settled on a fairly simple way that is [...]]]></description>
		<wfw:commentRss>http://clearcove.ca/blog/2008/08/recipe-restful-permissions-for-rails/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>OpenSource project: Quentin Time Tracker</title>
		<link>http://clearcove.ca/blog/2008/08/quentin-time-tracker/</link>
		<comments>http://clearcove.ca/blog/2008/08/quentin-time-tracker/#comments</comments>
		<pubDate>Sun, 10 Aug 2008 19:41:05 +0000</pubDate>
		<dc:creator>Jo Hund</dc:creator>
				<category><![CDATA[Ruby/Rails]]></category>
		<category><![CDATA[Tools]]></category>

		<guid isPermaLink="false">http://clearcove.ca/?p=142</guid>
		<description><![CDATA[Being a contract software developer, tracking my time is extremely important for my business: I need to write invoices with task break downs, I want to get better at estimating, and I am just curious about what I spend my time on.
So I filled this need by writing my own Rails time tracker: meet Quentin. [...]]]></description>
		<wfw:commentRss>http://clearcove.ca/blog/2008/08/quentin-time-tracker/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Require Ruby &#8216;Forwardable&#8217; on Leopard</title>
		<link>http://clearcove.ca/blog/2008/05/require-ruby-forwardable-on-leopard/</link>
		<comments>http://clearcove.ca/blog/2008/05/require-ruby-forwardable-on-leopard/#comments</comments>
		<pubDate>Wed, 14 May 2008 04:54:52 +0000</pubDate>
		<dc:creator>Jo Hund</dc:creator>
				<category><![CDATA[Note to self]]></category>
		<category><![CDATA[Ruby/Rails]]></category>

		<guid isPermaLink="false">http://new.clearcove.ca/?p=61</guid>
		<description><![CDATA[When I upgraded to Leopard, some of my Rails apps broke. Ruby threw this error at me:
uninitialized constant User::Forwardable
Here is a simple fix:

require 'forwardable'

in environment.rb.
It seems that on Tiger &#8216;Forwardable&#8217; was included by default, but not on Leopard any more. Not exactly sure why this is.
]]></description>
		<wfw:commentRss>http://clearcove.ca/blog/2008/05/require-ruby-forwardable-on-leopard/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Litespeed: The best kept Rails deployment secret</title>
		<link>http://clearcove.ca/blog/2008/01/litespeed-the-best-kept-rails-deployment-secret/</link>
		<comments>http://clearcove.ca/blog/2008/01/litespeed-the-best-kept-rails-deployment-secret/#comments</comments>
		<pubDate>Tue, 08 Jan 2008 04:47:31 +0000</pubDate>
		<dc:creator>Jo Hund</dc:creator>
				<category><![CDATA[Ruby/Rails]]></category>

		<guid isPermaLink="false">http://new.clearcove.ca/?p=58</guid>
		<description><![CDATA[There is a great way to deploy rails applications. I know it is being used on some high traffic production deployments. How come it never gets mentioned in any official Rails documentation?
Litespeed is its name. It is free — not open source though. And that may be the reason why you don&#8217;t hear much about [...]]]></description>
		<wfw:commentRss>http://clearcove.ca/blog/2008/01/litespeed-the-best-kept-rails-deployment-secret/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.390 seconds -->
