From 22ac1d96a685afe135428730ebc053fd80c671e6 Mon Sep 17 00:00:00 2001
From: Justin Thomas <justin@justinthomas.name>
Date: Sat, 24 Mar 2012 12:34:00 -0700
Subject: [PATCH] Add Resque.after_fork to correct problem with database
 connections and remove resque-ensure-connected

---
 Gemfile               | 1 -
 lib/tasks/resque.rake | 2 ++
 2 files changed, 2 insertions(+), 1 deletion(-)

diff --git a/Gemfile b/Gemfile
index 7393e34c9..4f978d144 100644
--- a/Gemfile
+++ b/Gemfile
@@ -85,7 +85,6 @@ gem 'ruby-oembed', '~> 0.8.7'
 # queue
 
 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 'SystemTimer', '1.2.3', :platforms => :ruby_18
 
diff --git a/lib/tasks/resque.rake b/lib/tasks/resque.rake
index fe3e5a16b..5365b6f35 100644
--- a/lib/tasks/resque.rake
+++ b/lib/tasks/resque.rake
@@ -3,6 +3,8 @@ require 'resque/tasks'
 task "resque:setup" do
   require File.join(File.dirname(__FILE__), '..', '..', 'config', 'environment')
   Rails.logger.info("event=resque_setup rails_env=#{Rails.env}")
+
+  Resque.after_fork = Proc.new { ActiveRecord::Base.establish_connection }
 end
 
 desc "Alias for resque:work (To run workers on Heroku)"