Resque scheduler

[crigor]

Uses Joe Heth's code from #75

[dvalfre]

it should be include_recipe 'resque_scheduler'

[dvalfre]

The main 'resque-scheduler' recipe has the following code:

  execute 'install resque gem' do
    command 'gem install resque redis redis-namespace yajl-ruby -r'
    not_if { 'gem list | grep resque' }
end

Which comes from the v4 recipe. According to engineyard/ey-cloud-recipes#150 that codes is faulty and evaluates to '1', which is why the gems get never installed.
Funnily enough, the 'resque-scheduler' works (in v4, and guess will do in v5) since the necessary Gems are included on the app's Gemfile.

Shall the aforemenationed code be dropped from the main 'resque-scheduler' recipe?

[radamanthus]

@dvalfre I agree, the gem dependencies should be in the Gemfile and the recipe should not bother with installing the gems.

[dvalfre]

For a clustered env, this line should be replaced with at least:

default['redis'].tap do |redis|

  # Collect the redis instances in this array
  redis_instances = []

  # Run Redis on a named util instance
  # This is the default
  redis['utility_name'] = 'resque'
  redis_instances << redis['utility_name']
  redis['is_redis_instance'] = (
    node['dna']['instance_role'] == 'util' &&
    redis_instances.include?(node['dna']['name'])
  )
end

and for a solo env with:

default['redis'].tap do |redis|

  # Collect the redis instances in this array
  redis_instances = []

 # Run redis on a solo instance
  # Not recommended for production environments
  #redis['is_redis_instance'] = (node['dna']['instance_role'] == 'solo') 
end

[dvalfre]

Shall we include this small Redis wrapper at all? Leaning towards adding a section on the Resque-Scheduler wrapper's Readme telling the customer to enable the full Redis recipe (as we do with Sidekiq).

[radamanthus]

I opened PR #150 to remove custom-redis from resque_scheduler