如何在 rake 任务中强制 RAILS_ENV? [英] How do I force RAILS_ENV in a rake task?
本文介绍了如何在 rake 任务中强制 RAILS_ENV?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!
问题描述
我有这个小任务:
namespace :db do
namespace :test do
task :reset do
ENV['RAILS_ENV'] = "test"
Rake::Task['db:drop'].invoke
Rake::Task['db:create'].invoke
Rake::Task['db:migrate'].invoke
end
end
end
现在,当我执行时,它将忽略我尝试硬编码的 RAILS_ENV.如何使这项任务按预期工作
Now, when I execute, it will ignore the RAILS_ENV I tried to hard-code. How do I make this task work as expected
推荐答案
对于这个特定的任务,你只需要改变 DB 连接,所以正如 Adam 指出的,你可以这样做:
For this particular task, you only need to change the DB connection, so as Adam pointed out, you can do this:
namespace :db do
namespace :test do
task :reset do
ActiveRecord::Base.establish_connection('test')
Rake::Task['db:drop'].invoke
Rake::Task['db:create'].invoke
Rake::Task['db:migrate'].invoke
ActiveRecord::Base.establish_connection(ENV['RAILS_ENV']) #Make sure you don't have side-effects!
end
end
end
如果你的任务更复杂,并且你需要 ENV 的其他方面,你最安全的方法是生成一个新的 rake 进程:
If your task is more complicated, and you need other aspects of ENV, you are safest spawning a new rake process:
namespace :db do
namespace :test do
task :reset do
system("rake db:drop RAILS_ENV=test")
system("rake db:create RAILS_ENV=test")
system("rake db:migrate RAILS_ENV=test")
end
end
end
或
namespace :db do
namespace :test do
task :reset do
if (ENV['RAILS_ENV'] == "test")
Rake::Task['db:drop'].invoke
Rake::Task['db:create'].invoke
Rake::Task['db:migrate'].invoke
else
system("rake db:test:reset RAILS_ENV=test")
end
end
end
end
这篇关于如何在 rake 任务中强制 RAILS_ENV?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!
查看全文