delayed-job

问题 I've used Delayed Job on Heroku's older stacks (Aspen and Bamboo), but with their new(ish) Cedar stack, I'd like to try something more efficient. The specific background jobs I'm performing are API calls to different carriers (UPS, FedEx, USPS, etc etc) and I typically am processing thousands every hour. I need to be able to process jobs concurrently to get through the queue quickly. On top of that, I'd like to try to reduce costs. On the previous stacks where I've been using Delayed Job, I

问题 I've used Delayed Job on Heroku's older stacks (Aspen and Bamboo), but with their new(ish) Cedar stack, I'd like to try something more efficient. The specific background jobs I'm performing are API calls to different carriers (UPS, FedEx, USPS, etc etc) and I typically am processing thousands every hour. I need to be able to process jobs concurrently to get through the queue quickly. On top of that, I'd like to try to reduce costs. On the previous stacks where I've been using Delayed Job, I

问题 SomeController#update (RestClient::ResourceNotFound) "Resource Not Found" I'm receiving this error (where previously I was not) while trying to enqueue delayed jobs using the autoscale branch of DelayedJob. This does not occur with a none autoscale branch but I'm at a loss to pinpoint what the problem is. If anyone is experiencing the same or can point me toward a likely cause I'd be grateful for advice. 回答1: Just a guess... Is it possible the ResourceNotFound is occurring because the heroku

问题 My app has deals where orders are made once a minimum order amount is met. Currently I have setup orders that that orders are placed right after the order is submitted which is all working. Now I need to change the process so that orders are processed once the minimum order number for the deal is met. Should I use delayed_job for this or maybe a cron process? Here is the process I was thinking of following. Delaying Orders Until Orders minimum is met Find deals that are still active Then find

问题 I've added the delayed_job gem to my gemfile and installed correctly but when I try to run the following line: Delayed::Job.enqueue do_it(), 0, 1.minutes.from_now.getutc I get the error 'uninitialized constant Delayed::Job' Can somebody explain what i need to do here? I've tried running 'rake jobs:work' beforehand but it also returns the 'uninitialized constant Delayed::Job' error. Additionally, I've added "require 'delayed_job'" to the file (application.rb) without much luck. 回答1: Did you

问题 I'm using Bundler for a Rails app deployed by Capistrano. I'm trying to add the DelayedJob gem, but the bin/delayed_job file is missing from the remote server after I do a deploy. It exists on my local machine. I tried manually creating it with bundle binstubs delayed_job but it fails with: There are no executables for the gem delayed_job. What am I missing here? The gems in question are: Bundler 1.3.5, Capistrano 3.1.0, DelayedJob 4.0.0, Rails 4.0.2 EDIT: Here is my full Gemfile: http:/

问题 I am trying to build api urls for password reset via. devise_token_auth gem. As per the usage mentioned here, the POST request for /api/v1/auth/password needs params email and redirect_url . The user matching the email param will be sent instructions on how to reset their password. redirect_url is the url to which the user will be redirected after visiting the link contained in the email. However, I am getting the following URL in the email for password reset, in which the param redirect_url

问题 Is there a parameter I can pass to delayed_job that will prevent it from deleting completed jobs from the delayed_jobs table? kind of like the destroy_failed_jobs but for completed jobs any ideas? 回答1: It doesn't appear so. From the README: https://github.com/tobi/delayed_job By default, it will delete failed jobs (and it always deletes successful jobs). If you want to keep failed jobs, set Delayed::Job.destroy_failed_jobs = false. The failed jobs will be marked with non-null failed_at. You

问题 I have a simple Procfile that reads: web: bundle exec rails server thin -p $PORT worker: bundle exec rake jobs:work On Heroku, this will launch N worker tasks, where N is whatever I've scaled it to be. On my development system, $ foreman start will only launch one worker task. If I want to launch three workers, I need a Procfile that looks like: web: bundle exec rails server thin -p $PORT worker: bundle exec rake jobs:work worker: bundle exec rake jobs:work worker: bundle exec rake jobs:work

问题 I have a simple Procfile that reads: web: bundle exec rails server thin -p $PORT worker: bundle exec rake jobs:work On Heroku, this will launch N worker tasks, where N is whatever I've scaled it to be. On my development system, $ foreman start will only launch one worker task. If I want to launch three workers, I need a Procfile that looks like: web: bundle exec rails server thin -p $PORT worker: bundle exec rake jobs:work worker: bundle exec rake jobs:work worker: bundle exec rake jobs:work