<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Rails upgraded to 1.1</title>
	<atom:link href="http://blog.dreamhosters.com/2006/03/29/rails-upgraded-to-11/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.dreamhosters.com/2006/03/29/rails-upgraded-to-11/</link>
	<description>Tips &#038; Tricks for Dreamhosters</description>
	<pubDate>Thu, 07 Aug 2008 21:02:24 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Unofficial DreamHost Blog</title>
		<link>http://blog.dreamhosters.com/2006/03/29/rails-upgraded-to-11/#comment-265</link>
		<dc:creator>Unofficial DreamHost Blog</dc:creator>
		<pubDate>Sun, 23 Apr 2006 09:06:32 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dreamhosters.com/2006/03/29/rails-upgraded-to-11/#comment-265</guid>
		<description>&lt;strong&gt;DreamHost Upgrades Rails Monday...&lt;/strong&gt;

In case you haven&#8217;t read it on the new DreamHost Status Page: DreamHost will start to roll out Ruby on Rails 1.1 early next week.
When they initially upgraded Rails to 1.1 three weeks ago a lot of application broke since Rails 1.1 isn&#8217;t 100...</description>
		<content:encoded><![CDATA[<p><strong>DreamHost Upgrades Rails Monday&#8230;</strong></p>
<p>In case you haven&#8217;t read it on the new DreamHost Status Page: DreamHost will start to roll out Ruby on Rails 1.1 early next week.<br />
When they initially upgraded Rails to 1.1 three weeks ago a lot of application broke since Rails 1.1 isn&#8217;t 100&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Downtime &#38; Lag</title>
		<link>http://blog.dreamhosters.com/2006/03/29/rails-upgraded-to-11/#comment-104</link>
		<dc:creator>Downtime &#38; Lag</dc:creator>
		<pubDate>Wed, 29 Mar 2006 22:53:33 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dreamhosters.com/2006/03/29/rails-upgraded-to-11/#comment-104</guid>
		<description>[...] I&#8217;m extremely sorry about all the downtime and lag lately. Dreamhost was trying be on the cutting edge by upgrading to Ruby on Rails 1.1 last night. Unfortunately, Typo does not currently support Rails 1.1. A post in the forums brought me back online using slow CGI this morning. [...]</description>
		<content:encoded><![CDATA[<p>[...] I&#8217;m extremely sorry about all the downtime and lag lately. Dreamhost was trying be on the cutting edge by upgrading to Ruby on Rails 1.1 last night. Unfortunately, Typo does not currently support Rails 1.1. A post in the forums brought me back online using slow CGI this morning. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Unofficial DreamHost Blog</title>
		<link>http://blog.dreamhosters.com/2006/03/29/rails-upgraded-to-11/#comment-103</link>
		<dc:creator>Unofficial DreamHost Blog</dc:creator>
		<pubDate>Wed, 29 Mar 2006 20:05:15 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dreamhosters.com/2006/03/29/rails-upgraded-to-11/#comment-103</guid>
		<description>Nuby on Rails also has the tip about &lt;a href="http://nubyonrails.topfunky.com/articles/2006/03/29/surviving-rails-1-1-with-server-monitoring" rel="nofollow"&gt;freezing your rails&lt;/a&gt; and also points to a simple &lt;a href="http://nubyonrails.topfunky.com/articles/2006/03/29/surviving-rails-1-1-with-server-monitoring" rel="nofollow"&gt;server monitoring tool&lt;/a&gt; you can run as a cronjob in order to get notified next time anything blow up.</description>
		<content:encoded><![CDATA[<p>Nuby on Rails also has the tip about <a href="http://nubyonrails.topfunky.com/articles/2006/03/29/surviving-rails-1-1-with-server-monitoring" rel="nofollow">freezing your rails</a> and also points to a simple <a href="http://nubyonrails.topfunky.com/articles/2006/03/29/surviving-rails-1-1-with-server-monitoring" rel="nofollow">server monitoring tool</a> you can run as a cronjob in order to get notified next time anything blow up.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Greg</title>
		<link>http://blog.dreamhosters.com/2006/03/29/rails-upgraded-to-11/#comment-102</link>
		<dc:creator>Greg</dc:creator>
		<pubDate>Wed, 29 Mar 2006 19:44:22 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dreamhosters.com/2006/03/29/rails-upgraded-to-11/#comment-102</guid>
		<description>In case you are too lazy to read the previous link.

Just run "rake freeze_gems" and you will be all good.</description>
		<content:encoded><![CDATA[<p>In case you are too lazy to read the previous link.</p>
<p>Just run &#8220;rake freeze_gems&#8221; and you will be all good.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Greg</title>
		<link>http://blog.dreamhosters.com/2006/03/29/rails-upgraded-to-11/#comment-101</link>
		<dc:creator>Greg</dc:creator>
		<pubDate>Wed, 29 Mar 2006 19:41:39 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dreamhosters.com/2006/03/29/rails-upgraded-to-11/#comment-101</guid>
		<description>This is the reason why the Ruby on Rails team recommends to "freeze" your application when using Rails on a shared host.

See the link below for more information (since following these simply recommendations will prevent future problems like this)

http://weblog.rubyonrails.org/articles/2005/12/22/freezing-your-rails-when-you-deploy-shared</description>
		<content:encoded><![CDATA[<p>This is the reason why the Ruby on Rails team recommends to &#8220;freeze&#8221; your application when using Rails on a shared host.</p>
<p>See the link below for more information (since following these simply recommendations will prevent future problems like this)</p>
<p><a href="http://weblog.rubyonrails.org/articles/2005/12/22/freezing-your-rails-when-you-deploy-shared" rel="nofollow">http://weblog.rubyonrails.org/articles/2005/12/22/freezing-your-rails-when-you-deploy-shared</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kellegous</title>
		<link>http://blog.dreamhosters.com/2006/03/29/rails-upgraded-to-11/#comment-100</link>
		<dc:creator>kellegous</dc:creator>
		<pubDate>Wed, 29 Mar 2006 19:38:41 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dreamhosters.com/2006/03/29/rails-upgraded-to-11/#comment-100</guid>
		<description>As Sean points out.

Sadly it is broken. And sadly that means all of us dreamhosters who are using rails 1.0 are also broken.

For those of us who are just watching the clock tick on the support request, here's a work-around that is working for me:

Add these two lines to the top of config/boot.rb in your rails project:

require 'rubygems'
require_gem 'rails', '1.0.0'</description>
		<content:encoded><![CDATA[<p>As Sean points out.</p>
<p>Sadly it is broken. And sadly that means all of us dreamhosters who are using rails 1.0 are also broken.</p>
<p>For those of us who are just watching the clock tick on the support request, here&#8217;s a work-around that is working for me:</p>
<p>Add these two lines to the top of config/boot.rb in your rails project:</p>
<p>require &#8216;rubygems&#8217;<br />
require_gem &#8216;rails&#8217;, &#8216;1.0.0&#8242;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: i survived</title>
		<link>http://blog.dreamhosters.com/2006/03/29/rails-upgraded-to-11/#comment-99</link>
		<dc:creator>i survived</dc:creator>
		<pubDate>Wed, 29 Mar 2006 19:08:35 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dreamhosters.com/2006/03/29/rails-upgraded-to-11/#comment-99</guid>
		<description>[...] I knew some people would figure it out. [...]</description>
		<content:encoded><![CDATA[<p>[...] I knew some people would figure it out. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sean Mountcastle</title>
		<link>http://blog.dreamhosters.com/2006/03/29/rails-upgraded-to-11/#comment-98</link>
		<dc:creator>Sean Mountcastle</dc:creator>
		<pubDate>Wed, 29 Mar 2006 13:40:47 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dreamhosters.com/2006/03/29/rails-upgraded-to-11/#comment-98</guid>
		<description>The upgrade to Rails 1.1 was botched as the gems for activerecord 1.14.0 and actionpack 1.12.0 were not installed.

gem list --local on holt shows the following:

[holt]$ gem list --local &#124; grep acti   
actionmailer (1.2.0, 1.1.5)
actionpack (1.11.2)
actionwebservice (1.1.0, 1.0.0)
activerecord (1.13.2)
activesupport (1.3.0, 1.2.5) 

Sean</description>
		<content:encoded><![CDATA[<p>The upgrade to Rails 1.1 was botched as the gems for activerecord 1.14.0 and actionpack 1.12.0 were not installed.</p>
<p>gem list &#8211;local on holt shows the following:</p>
<p>[holt]$ gem list &#8211;local | grep acti<br />
actionmailer (1.2.0, 1.1.5)<br />
actionpack (1.11.2)<br />
actionwebservice (1.1.0, 1.0.0)<br />
activerecord (1.13.2)<br />
activesupport (1.3.0, 1.2.5) </p>
<p>Sean</p>
]]></content:encoded>
	</item>
</channel>
</rss>

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