From 00993acfedd0b72e44102479ea85b5ad074cfea2 Mon Sep 17 00:00:00 2001 From: Seth Call Date: Wed, 30 Jul 2014 15:35:56 -0500 Subject: [PATCH] * VRFS-1988 set up infra to allow for scheduler.yml override file --- web/lib/tasks/scheduler.rake | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/web/lib/tasks/scheduler.rake b/web/lib/tasks/scheduler.rake index 099d915dc..387ff20ed 100644 --- a/web/lib/tasks/scheduler.rake +++ b/web/lib/tasks/scheduler.rake @@ -16,7 +16,15 @@ task :scheduler => :environment do # The schedule doesn't need to be stored in a YAML, it just needs to # be a hash. YAML is usually the easiest. - Resque.schedule = YAML.load_file(File.join(File.dirname(__FILE__), '../..', 'config/scheduler.yml')) + config = YAML.load_file(File.join(File.dirname(__FILE__), '../..', 'config/scheduler.yml')) + + if File.exist? File.join(File.dirname(__FILE__), '../..', 'config/scheduler_override.yml') + puts "scheduler_override file found. loading..." + override = YAML.load_file(File.join(File.dirname(__FILE__), '../..', 'config/scheduler_override.yml')) + config.merge!(override) + end + + Resque.schedule = config # If your schedule already has +queue+ set for each job, you don't # need to require your jobs. This can be an advantage since it's