<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/css" href="/stylesheets/rss.css"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>5Valleys Blog</title>
    <link>http://5Valleys.com/tags/#{params[:tag_id]/posts</link>
    <language>en-us</language>
    <ttl>40</ttl>
    <description>Rails, Software Development, Western Montana, and other incoherent ramblings.</description>
    <item>
      <title>Special RAILS_ENV for Cron</title>
      <description>I have a site with a cron that runs a Rake task every minute to do a few maintenance tasks.
A user reported a problem and I went to look at the production log file to investigate, only to discover another problem. The cron task was quickly filling up the production log file. I have the environment.rb setting to rotate the logs, so it wasn't filling the server, but also meant that when I needed to go look at the logs, I only had about an hours worth, and the problem occurred an hour and a half ago. All log entries from the time the problem occurred had already been rotated out of existence. So, here's the solution I came up with. &lt;a href='http://www.5valleys.com/posts/22-Special-RAILS-ENV-for-Cron'&gt;continue...&lt;/a&gt;</description>
      <pubDate>Tue, 04 Sep 2007 23:02:08 -0600</pubDate>
      <link>http://www.5valleys.com/posts/22-Special-RAILS-ENV-for-Cron</link>
      <author>jsgarvin</author>
      <category>Rails</category>
      <category>Cron</category>
    </item>
  </channel>
</rss>
