Global Reset

I’m having some problems with Typo. For a while, I was getting a completely unresponsive blog, requiring a “killall -9 dispatch.fcgi && rake sweep_cache” to bring it back to life. I had assumed that when Dreamhost said that it was taking the Rails environment to Production, that meant that our virtual host entries would declare: RAILS_ENV = production. I found at least one person who also thought as much. Apparently, they are still defaulting to development mode, so I edited config/environment.rb and changed the RAILS_ENV line to read thusly:

RAILS_ENV  = 'production'

Once I did, I noticed that the blog hasn’t become completely non-responsive since and it seems to be responding a lot faster. I still have some bugs to work out though, as I’m seeing way too many “dispatch.fcgi” processes start up. I wrote an email to the mailing list and hopefully I’ll get some more help on that.

There are a couple of .htaccess tidbits that you may be interested in as well. If you, like me, migrated from Wordpress, here are the entries I used to forward my old Wordpress articles to the new Typo pages:

Redirect /blog/archives http://blog.globalreset.org/articles
Redirect /blog http://blog.globalreset.org

And here is my .htaccess entry I inserted into the public/.htaccess file in my Typo install dir so that I could still access my /stats subfolder (otherwise, Typo tries to interpret the url instead of letting it open my web stats page generated by Dreamhost):

#allow /stats
RewriteCond %{REQUEST_URI} ^/stats/(.)$ [OR]
RewriteCond %{REQUEST_URI} ^/failed_auth.html$
RewriteRule ^.$ - [L]

Also, if you’re reading this with an RSS reader, you’re missing out on the new layout of my site. Come to the home page and let me know what you think of my banner.

Technorati Tags: RubyOnRails, Typo