<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2.3" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: FastCGI Environment Changes for Rails - Updated</title>
	<link>http://www.dreamhoststatus.com/2008/03/14/fastcgi-environment-changes-for-rails/</link>
	<description>Information about DreamHost Services</description>
	<pubDate>Sat, 17 May 2008 13:54:26 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.3</generator>

	<item>
		<title>By: db</title>
		<link>http://www.dreamhoststatus.com/2008/03/14/fastcgi-environment-changes-for-rails/#comment-157637</link>
		<dc:creator>db</dc:creator>
		<pubDate>Tue, 08 Apr 2008 00:45:22 +0000</pubDate>
		<guid>http://www.dreamhoststatus.com/2008/03/14/fastcgi-environment-changes-for-rails/#comment-157637</guid>
		<description>Sending out an email might have been difficult to get all the users but I warning here would have helped.</description>
		<content:encoded><![CDATA[<p>Sending out an email might have been difficult to get all the users but I warning here would have helped.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Grey Hodge</title>
		<link>http://www.dreamhoststatus.com/2008/03/14/fastcgi-environment-changes-for-rails/#comment-141721</link>
		<dc:creator>Grey Hodge</dc:creator>
		<pubDate>Tue, 18 Mar 2008 05:54:29 +0000</pubDate>
		<guid>http://www.dreamhoststatus.com/2008/03/14/fastcgi-environment-changes-for-rails/#comment-141721</guid>
		<description>How about you host a copy in production mode, then make changes in your local repo and sync them, like the rest of us?</description>
		<content:encoded><![CDATA[<p>How about you host a copy in production mode, then make changes in your local repo and sync them, like the rest of us?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan A</title>
		<link>http://www.dreamhoststatus.com/2008/03/14/fastcgi-environment-changes-for-rails/#comment-141591</link>
		<dc:creator>Ryan A</dc:creator>
		<pubDate>Mon, 17 Mar 2008 22:12:59 +0000</pubDate>
		<guid>http://www.dreamhoststatus.com/2008/03/14/fastcgi-environment-changes-for-rails/#comment-141591</guid>
		<description>Wow. I had to come here to figure it out.
I wondered wtf was going on. Lovely. Even though my dev is behind passwords so only a few people can access it. I'd have to second @Bart as well in that if you run dev in a production mode for testing purposes and only avail to a few users this should be allowable.

Oh well, at least I can hack around this latest adjustment. :)</description>
		<content:encoded><![CDATA[<p>Wow. I had to come here to figure it out.<br />
I wondered wtf was going on. Lovely. Even though my dev is behind passwords so only a few people can access it. I&#8217;d have to second @Bart as well in that if you run dev in a production mode for testing purposes and only avail to a few users this should be allowable.</p>
<p>Oh well, at least I can hack around this latest adjustment. <img src='http://www.dreamhoststatus.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Annie Niemoose</title>
		<link>http://www.dreamhoststatus.com/2008/03/14/fastcgi-environment-changes-for-rails/#comment-141576</link>
		<dc:creator>Annie Niemoose</dc:creator>
		<pubDate>Mon, 17 Mar 2008 21:17:59 +0000</pubDate>
		<guid>http://www.dreamhoststatus.com/2008/03/14/fastcgi-environment-changes-for-rails/#comment-141576</guid>
		<description>I'd have to second @Bart here.  Everyone seems to be discussing this (especially the OP) as if dev and production were the only options.  Where, exactly, are we supposed to host staging environments?</description>
		<content:encoded><![CDATA[<p>I&#8217;d have to second @Bart here.  Everyone seems to be discussing this (especially the OP) as if dev and production were the only options.  Where, exactly, are we supposed to host staging environments?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Torsten</title>
		<link>http://www.dreamhoststatus.com/2008/03/14/fastcgi-environment-changes-for-rails/#comment-141550</link>
		<dc:creator>Torsten</dc:creator>
		<pubDate>Mon, 17 Mar 2008 19:47:50 +0000</pubDate>
		<guid>http://www.dreamhoststatus.com/2008/03/14/fastcgi-environment-changes-for-rails/#comment-141550</guid>
		<description>Hey guys,

this IS something you need to send mails out to at least all those people who are actually using rails! I don't mind testing my app in production instead of development, but IT IS NOT NICE even for people who are testing it to suddenly see a broken app. 

Like I said: Let people know a day or two before you do stuff like that!</description>
		<content:encoded><![CDATA[<p>Hey guys,</p>
<p>this IS something you need to send mails out to at least all those people who are actually using rails! I don&#8217;t mind testing my app in production instead of development, but IT IS NOT NICE even for people who are testing it to suddenly see a broken app. </p>
<p>Like I said: Let people know a day or two before you do stuff like that!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bart</title>
		<link>http://www.dreamhoststatus.com/2008/03/14/fastcgi-environment-changes-for-rails/#comment-141486</link>
		<dc:creator>Bart</dc:creator>
		<pubDate>Mon, 17 Mar 2008 15:57:32 +0000</pubDate>
		<guid>http://www.dreamhoststatus.com/2008/03/14/fastcgi-environment-changes-for-rails/#comment-141486</guid>
		<description>Thank you, you just successfully blocked staging sites. The purpose of a staging site is to get feedback from testers and ensures it works in an environment close to production. 

How about low band width developers who can't run 

That you made this change without prior warning shows your contempt for rails developers. Couldn't you have considered other options like throttling?

Thanks dreamhost!</description>
		<content:encoded><![CDATA[<p>Thank you, you just successfully blocked staging sites. The purpose of a staging site is to get feedback from testers and ensures it works in an environment close to production. </p>
<p>How about low band width developers who can&#8217;t run </p>
<p>That you made this change without prior warning shows your contempt for rails developers. Couldn&#8217;t you have considered other options like throttling?</p>
<p>Thanks dreamhost!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Grey Hodge</title>
		<link>http://www.dreamhoststatus.com/2008/03/14/fastcgi-environment-changes-for-rails/#comment-141404</link>
		<dc:creator>Grey Hodge</dc:creator>
		<pubDate>Mon, 17 Mar 2008 09:16:43 +0000</pubDate>
		<guid>http://www.dreamhoststatus.com/2008/03/14/fastcgi-environment-changes-for-rails/#comment-141404</guid>
		<description>No, see, if you were running in DEV mode on a production site, you're dumb. You get no warning. If you were running DEV mode on a DEV site, moving it to a local DEV box won't kill you because, hey, it wasn't live! And everyone else gets snappy sites again. Go bitch about downtime and how you're losing billions.</description>
		<content:encoded><![CDATA[<p>No, see, if you were running in DEV mode on a production site, you&#8217;re dumb. You get no warning. If you were running DEV mode on a DEV site, moving it to a local DEV box won&#8217;t kill you because, hey, it wasn&#8217;t live! And everyone else gets snappy sites again. Go bitch about downtime and how you&#8217;re losing billions.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thanks!</title>
		<link>http://www.dreamhoststatus.com/2008/03/14/fastcgi-environment-changes-for-rails/#comment-141244</link>
		<dc:creator>Thanks!</dc:creator>
		<pubDate>Sun, 16 Mar 2008 21:59:37 +0000</pubDate>
		<guid>http://www.dreamhoststatus.com/2008/03/14/fastcgi-environment-changes-for-rails/#comment-141244</guid>
		<description>Thanks for fixing this issue.</description>
		<content:encoded><![CDATA[<p>Thanks for fixing this issue.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: openBack</title>
		<link>http://www.dreamhoststatus.com/2008/03/14/fastcgi-environment-changes-for-rails/#comment-141198</link>
		<dc:creator>openBack</dc:creator>
		<pubDate>Sun, 16 Mar 2008 17:37:07 +0000</pubDate>
		<guid>http://www.dreamhoststatus.com/2008/03/14/fastcgi-environment-changes-for-rails/#comment-141198</guid>
		<description>Mike Boone: I had the same errors you had and had to restart dispatch and all was well. Thanks once again for killing sites and throwing away our customers, DreamHost.</description>
		<content:encoded><![CDATA[<p>Mike Boone: I had the same errors you had and had to restart dispatch and all was well. Thanks once again for killing sites and throwing away our customers, DreamHost.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Derailed</title>
		<link>http://www.dreamhoststatus.com/2008/03/14/fastcgi-environment-changes-for-rails/#comment-141069</link>
		<dc:creator>Derailed</dc:creator>
		<pubDate>Sun, 16 Mar 2008 03:38:06 +0000</pubDate>
		<guid>http://www.dreamhoststatus.com/2008/03/14/fastcgi-environment-changes-for-rails/#comment-141069</guid>
		<description>Maybe you shouldn't use Rails period. You spend 80% of your time solving stupid performance problems.</description>
		<content:encoded><![CDATA[<p>Maybe you shouldn&#8217;t use Rails period. You spend 80% of your time solving stupid performance problems.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
