• remember you can always debug stuff (further then the really informative “Rails application didn’t start properly”) starting webrick server via SSH on a random port (using the -p switch).
• remember you are switching to production, so you need to create the database, setup database.yml, migrate your schema and setup RAILS_ENV accordingly.
• if deploying to Dreamhost, install the Dreamhost Plugin
• Capistrano is your friend! (watching “rake deploy” going through its tasks is a lovely feeling)

About the photo disclaimer: no white powder was used to write this post nor to develop my webapp.

Technorati Tags: Programming Rails

First this. Now I realize giving a database field the same name of a Object public instance method wasn’t the best idea I could have.
Stupid errors I know. But it’s nice to learn things the hard way. You won’t forget easily thereafter.
Anyway I couldn’t start coding this project any worse :P This makes HTML look like a joyful land of peace as opposed to Ruby/Rails land evil. But evil is in the eyes of the beholder or of the dumb programmer.

Technorati Tags: Programming Rails

“link_to/url_for and related uses the ActionController::Base @url
instance variable to generate URLs, so if you (or plugins you’ve
installed) clobber it somehow, you’ll get this error.”
Thanks eden li via rails-talk. (for the Rails aware: I have a model named Url, so go figure how scaffolding named the instance variables in the associated controller :P )

Technorati Tags: Programming Rails