Closed josegonzalez closed 11 years ago
Note, this was caused by me being a dumbass and not properly calling Resque::setBackend()
with your updated configure paths.
As long as you enqueue jobs with CakeResque::enqueue()
instead of Resque::enqueue()
, you should never have issues with redis connection. Resque::setBackend()
will be set automatically.
This was when running the cake shell, not enqueuing the jobs. On Oct 3, 2012 10:49 AM, "Wan Qi Chen" notifications@github.com wrote:
As long as you enqueue jobs with CakeResque::enqueue() instead of Resque::enqueue(), you should never have issues with redis connection. Resque::setBackend() will be set automatically.
— Reply to this email directly or view it on GitHubhttps://github.com/kamisama/Cake-Resque/issues/12#issuecomment-9108840.
Ah ok.
Resque::setBackend()
should called in Lib/CakeResque.php, a file automatically required at the end of the bootstrap.php
In the shell, whenever you call
That does not set a port or anything for the Redis class. So then it tries to connect to null which fails.