Closed. This question is off-topic. It is not currently accepting answers. Want to improve this question? Update the question so it's on-topic for Stack Overflow.
I\'m a little confused because I hadn\'t set up any workers (on Heroku) and when I did Resque.enqueue the job was added to the queue (but not completed) so I\'m assuming the main thread generated the
I want to know if there are any good solutions for autoscaling dynos AND workers on Heroku in a production environment (probably a different solution for each of those, as they are pretty unrelated).
I am running rails 3.1rc4 and keep running into this error message in my resque queues uninitialized constant Net::SFTP With the exception \"NameError\"
My Resque job basically takes params hash and stores it into the DB. In the process it does several reads and writes.
I am currently using Resque for dealing with background jobs in my application. Now i have 5 different queues at present (it ll grow very fast). Each of them is doing works like updating Solr indexes,
I set up an EC2 instance using the Rubber gem. I\'m trying to use Redis/Resque to create a zip file.The command works fine when I run it from a Rails console, but when Redis/Resque tries it gets a per
I\'ve been trying to apply Square\'s method of including Resque in their integration tests without much luck. I\'m not sure if Resque and/or Cucumber has 开发者_JAVA技巧changed a lot since August 2010
I am using resque in my application for delayed jobs, where i cant send emails & sms to bulk number of users asynchronously. And the data is stored in mongodb, mongoid is the ODM connects rails &a
Resque jobs are just plain old ruby objects.I can use puts calls inside them to produce output into the console, or I can instantiate a standard Ruby Logger class with STDOUT and use that.