Often production and staging share much, so why not use a common file for that…

#config/environments/production.rb and config/environments/staging.rb
eval(File.read("#{File.dirname(__FILE__)}/production_like.rb"))
...environment specific code ...

#config/environments/production_like.rb
config.cache_classes = true
...

the File.read/eval is rather hacky, but works nevertheless 😉

How to get “x[y][z]” out of a hash ?

This made life with our form helpers a lot easier, since they take normal or nested keys <-> name of the input and prefilled value through params.

Any alternative is appreciated, since its pretty complex/hacky, the name is weird too …
(a simple to_query.split(‘=’)).inject… can work too, but would stringify all values and keys)

Usage

{'x'=>{'y'=>{'z'=>1}}}.value_from_nested_key('x[y][z]') == 1

Code

class Hash
  # {'x'=>{'y'=>{'z'=>1}}.value_from_nested_key('x[y][z]') => 1
  def value_from_nested_key(key)
    if key.to_s.include?('[')
      match, first, nesting = key.to_s.match(/(.+?)\[(.*)\]/).to_a
      value = self[first]
      nesting.split('][').each do |part|
        return nil unless value.is_a?(Hash)
        value = value[part]
      end
      value
    else
      self[key]
    end
  end
end

Instead of flipping values around by hand and possibly making mistakes, simply put an ‘un’ before them

Usage

class RenameStuff < ActiveRecord::Migration
  def self.up
    rename_column :users, :username, :login
    rename_column :users, :e_mail, :email
  end

  def self.down
    # simply cody and add 'un'
    unrename_column :users, :username, :login
    unrename_column :users, :e_mail, :email
  end
end

Code

# convenience method, so that rename statements do not need to be reversed by hand
class ActiveRecord::ConnectionAdapters::Table
  def unrename(a,b)
    rename b,a
  end
end
module ActiveRecord::ConnectionAdapters::SchemaStatements
  def unrename_column(table_name, a, b)
    rename_column(table_name, b, a)
  end
end