This post originated from an RSS feed registered with Ruby Buzz by Andrew Montgomery. Original Post: Rails code that doesn't get executed for generations and migrations Feed Title: Dark Liquid - Ruby Feed URL: http://feeds.feedburner.com/DarkLiquid-Ruby Feed Description: Ruby and Rails related ramblings by Andrew Montgomery Latest Ruby Buzz Posts Latest Ruby Buzz Posts by Andrew Montgomery Latest Posts From Dark Liquid - Ruby

At work, we���ve developed some plugins that cause issues when invoked in generators. For instance, you may be creating controllers on the fly, and so when you what to generate a controller to override the automatic one, you can���t as it is ���reserved���.

Well, you can determine what context in which you code is being executed quite easily using built in globals in Ruby.

To elaborate on the boss���s original post

  $0 # returns the command executed to run this script, i.e. script/generate, rake, etc

  unless $0 =~ /generate$/
    puts "Code that wont run in generators goes here"
  end

  if $0 == 'rake' and ARGV[0] =~ /migrate$/
    puts "special code to be run in migrations, like some cool migrations enhancing plugin for instance"
  end

I���d love to wrap this in a nice plugin, patch or gem to enable cool things like this:

if ['db:migrate', 'db:schema:load', 'db:schema:dump'].include?(Rails.rake_task) or Rails.run_by?('script/generate')
  puts "do cool stuff"
end