Background Process for Rails with access to ActiveRecord?

Question

I am planning to write a script for a Rails app that will be constantly running and needs access to the ActiveRecord instance.

I've looked into Sidekiq and Resque but am not quite sure which tool is best for the job (access to ActiveRecord and constantly running in the background asynchronously from the main application).

Also, after reading about Sidekiq / Resque, I believe that those two solutions may be too heavyweight for what I want to do ( add some data to ActiveRecord ).

Anybody have experience with this?

Any help or tips would be appreciated. Thanks.

check that link: http://stackoverflow.com/questions/11580954/resque-vs-sidekiq — zrl3dx, Jan 02 '14 at 23:27
whit that little Info, both work for what you need, both hace accede to activerecord, i'm not sufre what you mean with 'the activerecord ''instance'' — arieljuod, Jan 02 '14 at 23:32
You can also look at "delayed_jobs". But I suspect all you need is `require File.expand_path('../../config/boot', __FILE__)`. That's how any old Ruby scripts gets access to the Rails environment. — Phlip, Jan 02 '14 at 23:42

score 2 · Accepted Answer · answered Jan 02 '14 at 23:40

I defined a class to run rufus-scheduled job, I use a rake task to run this class, then use foreman to define a job in Procfile, and export to upstart (http://michael.vanrooijen.io/articles/2011/06/08-managing-and-monitoring-your-ruby-application-with-foreman-and-upstart/)

class XXXX
  def initialize
    @scheduler = Rufus::Scheduler.start_new
  end

  def run

    @scheduler.every '120s' do
      #run code
    end


    @scheduler.join


  end
end


task :rake_task => :environment do
  require "class file path"
  obj = XXXX.new
  obj.run

end

In Procfile

background_jobs:      rake rake_task

Background Process for Rails with access to ActiveRecord?

1 Answers1