Add Resque.after_fork to correct problem with database connections and remove resque-ensure-connected

This commit is contained in:
Justin Thomas 2012-03-24 12:34:00 -07:00
parent a0d6df6afa
commit 22ac1d96a6
2 changed files with 2 additions and 1 deletions

View file

@ -85,7 +85,6 @@ gem 'ruby-oembed', '~> 0.8.7'
# queue # queue
gem 'resque', '1.20.0' gem 'resque', '1.20.0'
gem 'resque-ensure-connected', :git => 'git://github.com/socialcast/resque-ensure-connected.git'
gem 'resque-timeout', '1.0.0' gem 'resque-timeout', '1.0.0'
gem 'SystemTimer', '1.2.3', :platforms => :ruby_18 gem 'SystemTimer', '1.2.3', :platforms => :ruby_18

View file

@ -3,6 +3,8 @@ require 'resque/tasks'
task "resque:setup" do task "resque:setup" do
require File.join(File.dirname(__FILE__), '..', '..', 'config', 'environment') require File.join(File.dirname(__FILE__), '..', '..', 'config', 'environment')
Rails.logger.info("event=resque_setup rails_env=#{Rails.env}") Rails.logger.info("event=resque_setup rails_env=#{Rails.env}")
Resque.after_fork = Proc.new { ActiveRecord::Base.establish_connection }
end end
desc "Alias for resque:work (To run workers on Heroku)" desc "Alias for resque:work (To run workers on Heroku)"