< Return to Blog

Getting Resque, Rails 4.2, and Unicorn to play nice

Having read Deploying Rails Applications with Unicorn this hit me as a surprise when I traced this issue all the way to my app's Unicorn error log, where it complained that Resque.redis did not implement the method #quit — a simple NoMethodError.

I consulted the Resque 2.0.0.pre.1 source for clues and found that the Resque module only had a reader defined Resque.redis= and the actual Redis instance was stored in its Config module.

Thanks to a convenience reader method, this is easily fixed by calling Resque.config.redis.quit instead.