With Rails3, it is no longer possible (well soon to be deprecated) to do: $ RAILS_ENV=test rake db:migrate So what''s the new way of doing it? -- Posted via http://www.ruby-forum.com/. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
I believe it is still ok to use RAILS_ENV as an environment variable outside of Rails, but you want to use Rails.env in your code. Sarah http://www.ultrasaurus.com/ -- Posted via http://www.ruby-forum.com/. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
Reasonably Related Threads
- rake migrate RAILS_ENV="production"
- rake db:migrate_plugins RAILS_ENV=production fails with "no such file to load -- initializer"
- Rails 3 "RAILS_ENV not defined by config/boot" error
- Rails3: "rake test" task does not run tests.
- How to set environment when calling rake task inside another