When using passenger fusion for hosting your rails sites, the rails process is owned by the user who owns config/environment.rb

So make sure that user can write to /tmp, /log and /public !

If you want your session to be valid across multiple sub-domains, here is how you do it:

 config.action_controller.session = {

 

if you get this error after upgrading to Rails 2.2.2:

 

!!! The bundled mysql.rb driver has been removed from Rails 2.2. Please install the mysql gem and try again: gem install mysql.

 

 

sudo env ARCHFLAGS="-arch i386" gem install mysql -- \
  --with-mysql-dir=/usr/local/mysql --with-mysql-lib=/usr/local/mysql/lib \
  --with-mysql-include=/usr/local/mysql/include

 

if you want to check if an object has an associated attribute method:

if a person has_one image and a gallery has_many images:

gallery.respond_to?(:images)
# => true
gallery.respond_to?(:image)
# => false
person.respond_to?(:images)
# => false
person.respond_to?(:image)
# => true

It looks like Rails 2.0 will no longer pay attention to the return value of before_filters. Currently, in our Pre-Rails 2.0 world, before_filters stop processing a request when they encounter a return value of false. You may recognize the common pattern:

  redirect_to new_session_path && return false

Rails 2.0 won't require a return value of false for a before_filter to stop the action, but will instead look to see if you called redirect_to or render. If either of these functions are called the filter chain is halted. This should clean up a lot of code and remove a lot of repetition. At the end of the day your before filters look almost the same as they always have, just drop the

&& return false