similar to: example for standalone?

Displaying 20 results from an estimated 7000 matches similar to: "example for standalone?"

2007 Mar 02
1
example standalone error.
Hello, Trying to get the example to work in standalone mode. I have the following in a file and am not certain why I get this undefined method error: error: ~/ruby sample_app.rb my sample app :) sample_app.rb:9: undefined method `new_worker'' for BackgrounDRb::MiddleMan:Class (NoMethodError) ### code follows ### # sample_app ... try to get stand-alone happiness. #require
2007 Mar 08
1
cant fully capture child output
I cant seem to get the io from a child process of a worker back to my client. There most be something academic I''m missing :/. I looked at examples in Pickaxe and Ruby PLEAC library ... and I believe the following should work: # called from within do_work... def backup(repo) logger.info(''SvnWorker backup repo ''+repo) tmp = [] my_project =
2007 Jun 21
0
config file questions
example: :host: 192.168.1.101 :protocol: druby :worker_dir: lib/workers :rails_env: production :pool_size: 15 :load_rails: true :timer_sleep: 60 :acl: :deny: all :allow: localhost 192.168.1.* :order: deny allow I have this config file on 2 app servers running rails. The 2 servers are running behind a load balancer. I''m starting the backgroundrb server on the one server with the
2007 Oct 12
0
Trouble on Multi Server setup
Hello all, I''m having some trouble getting backgroundrb set up so that all the processing happens on a single machine. I have 3 load balanced machines. Right now, all three run our web application and create MiddleMan workers to generate a large PDF report. However, because of the processing power needed to generate the PDFs, I want to change our setup so that two servers run
2006 Aug 07
2
uninitialized constants in worker class
I am new to this list and relatively new to the backgroundrb plugin,. So first i will say hello to everybody here, especially to Ezra Zygmuntowicz! I played a little bit with a dummy worker and so far everything worked well. But now i want to do real work in a worker but now i get that error[1]. It looks like that the constants configured in environment* configs are not available to the worker
2007 Dec 30
3
A newbie question regarding BackgroundRb
Hi all, I just read Ezra''s article on BackgroundRb and decided to use it one of my projects. I installed the plugin into my rails project using script/plugin and then ran rake backgroundrb:setup to copy the yml scripts. Now my backgroundrb.yml looks like ======= --- port: "22222" timer_sleep: 60 load_rails: true environment: development host: localhost database_yml:
2006 Aug 07
1
:load_rails
if CONFIG[''load_rails''] ActiveRecord::Base.allow_concurrency = true ActiveRecord::Base.establish_connection(YAML.load(ERB.new(IO.read ("#{RAILS_ROOT}/#{CONFIG[''database_yml'']}")).result)[CONFIG[''environment'']]) end if i read the code right, this option doesnt really load rails. wouldnt it be better (for those who rely on the
2006 Sep 15
2
unable to figure out how to get backgroundrb.yml to be used when starting backgroundrb
i ran rake backgroundrb:setup and modified the default config/backgroundrb.yml file as: --- port: "22223" timer_sleep: 60 load_rails: true environment: production host: localhost database_yml: config/database.yml acl: deny: all allow: localhost 127.0.0.1 order: deny,allow and my database.yml production: adapter: mysql database: chip2_production username: xxxxx password:
2007 Mar 02
0
example standalone error ... but if i ...
If I add .instance in front of new_worker I get the following error ... but for some reason i cant call new_worker directly...? error: ruby sample_app.rb my sample app :) ./backgroundrb/middleman.rb:440:in `ex'': undefined method `synchronize'' for nil:NilClass (NoMethodError) from ./backgroundrb/middleman.rb:401:in `[]'' from
2006 Nov 27
1
rails environment loaded but one plugin is undefined (using backgroundrb 0.2.0)
Hello all, I''m using BackgroundRb 0.2.0 (standalone) and in the do_work method of my worker, I''m working with objects from my Rails application. So in my config/backgroundrb.yml file, I added this line: :load_rails: true I think my worker isn''t doing what I want him to do. So I opened the console and read these error lines: # ruby script/backgroundrb console
2006 Jun 12
5
New release!
Hey Folks- I have just pushed a new release of BackgrounDRb to rubyforge. It has some nice new features to allow for usage of your ActiveRecord Models within your worker classes. I also added a config file for setting hosts and ports and if you want to load rails or not. Please have a look and let me know if anyone runs into any issues. If you already have an older version installed
2006 Sep 24
5
Can''t Connect to BackgroundRB
I''m having trouble getting backgroundrb up and running in a production environment. Here''s my backgroundrb.yml: --- port: "22222" timer_sleep: 60 load_rails: true environment: production host: XXX.XX.XXX.50 database_yml: config/database.yml acl: deny: all allow: localhost 127.0.0.1 XXX.XX.XXX.51 order: deny,allow I start BackgroundRB from XXX.XX.XXX.50 with
2006 Dec 04
4
Question about acls
Hi, I''m not much of a developer but I''ve been using backgroundrb for a while now and with the release of 0.2.1 it looks like I can finally upgrade from the old version (0.2.0 had some weird issues when jobs just wouldn''t run, seems to have cleared up now - Thanks!). Anyhow, while I''m doing this, I would like to tackle this problem. Most tasks I run in
2007 Aug 08
3
Cannot start workers in production mode
I have a job that I am starting from a Rails controller in production mode using MiddleMan: MiddleMan.new_worker(:class => :import_ccg_category_worker, :args => { :category_id => @category.id, :remote_category_id => params[:remote_category_id], :description => "Importing CCG products for #{@ category.name}" }) Both of the category ID variables are just basic integers. I
2006 Aug 29
1
Tasks get executed twice with repeat_every
I have a simple worker that I set up with repeat_every: class DueNoteQueuerWorker < BackgrounDRb::Rails repeat_every 1.minutes first_run Time.now def do_work(args) @logger.debug("Sending due notes. The current time is #{Time.now}") end end I want this to run every minute, all the time. The first run is fine, but it seems that subsequent runs get executed
2006 Jul 19
3
BackgrounDRb not working properly with files ?
Hey there, I''m kinda new to BackgrounDRb but I''m facing a big problem which I can''t seem to wrap my head around. The short version of it is : code that works when tested inside RoR''s console doesn''t work when executed by a BackgrounDRb worker. So I''ve tried a lot of things, including checking that the "load_rails" was true in the
2007 Sep 24
3
Trouble using backgroundrb
Hi all, I''m a newbie to backgroundrb and am having trouble integrating it into my rails-app. I''m using namespaces to differentiate between the parts of my app. When I want to create a new worker, it seems that it cannot find the worker object. Here''s my code: -------------------- controller app/passwd/index -------------------- class Passwd::IndexController <
2006 Jul 07
4
Problems with ActiveRecord in workers
Hi *, are there some special settings except of "load_rails: true" to make ActiveRecord models accessible within my workers? I''ve just installed the latest version of this great plugin, but I keep getting undefined method [] for #<DRb::DRbUnknown:0x12345> (line 105 in backgroundrb.rb) when one of the arguments for the worker is an ActiveRecord object. I assume that
2007 Mar 13
3
Scheduled worker dies after about 30-45 runs
I have a scheduled worker that runs every minute, checking for new eBay auctions to post. If it finds an auction, then it posts it. If there are no auctions in the database that are queued up, it simply does nothing. I got the worker to finally run as a scheduled worker, every minute. However, after about 30-45 scheduled runs, it simply stops running. My backgroundrb_schedules.yml file: ------
2006 Aug 25
0
Small Update: load_rails now actually loads rails
Folks- After enough people running into problems because load_rails was misleading and actually only loaded your models and ActiveRecord, I have just pushed a small update> All that has changed is that in the config file load_rails is set to true by default and it actually loads all of rails by require''ing environment.rb. SO anything that works in your rails app should be