similar to: Breakpointer and BackgrounDRb

Hey all, I''ve come accross BackgrounDRb and I have to say it''s a wounderful piece of software. It has the potential to solve so many of the problems that I am facing with a current RoR project. Like many others I was having issues with the scheduling side of things, I noticed that hemant said there was a new version coming out. So I checked out the version from trunk, and have

Seems this mail did not make it to the list for some reason. It contains my solution for the problem with login_engine without having to load the whole Rails environment. Begin forwarded message: > From: G?nter Ladwig <gladwig at gmx.de> > Date: 22. Juni 2006 23:51:18 MESZ > To: backgroundrb-devel at rubyforge.org > Subject: Re: [Backgroundrb-devel] Models and Backgroundrb

Hi, all. Just wondering if anyone has tried using the Paperclip file upload plugin with Backgroundrb. My current implementation uses attachment_fu - I save the file initially to the file system without generating thumbs, then a bdrb process picks up that file, generates thumbs, and saves to S3. This works fine and dandy, the only hitch is I want to save image metadata in the same table

Cc''ing to the list for archival purposes: On Tue, Mar 25, 2008 at 7:55 PM, Brian Noguchi <brian.noguchi at gmail.com> wrote: > Hi Hemant, > > I''m Brian Noguchi, a developer in the Bay Area. I have some questions about > backgroundrb, and I found your contact info on a forum. I figured its > probably best to get answers straight from the source. > >

Hemant We''ve continued testing our application with backgroundrb and found a couple of other problems when transfering large amounts of data. Both of these problems are still present in the github version of code. The first problem is an exception in the Marshal.load call in the receive_data method in the Packet::MetaPimp class. The root cause is in the BinParser module, in the arm of

I''m getting the following error (when doing script/backgroundrb start) on my local machine, which is running os x 10.4.11. However, it works just fine on my linux server. RAILS_ROOT/vendor/plugins/backgroundrb/lib/../framework/nbio.rb:64:in `dump_object'': undefined method `write_nonblock'' for #<UNIXSocket: 0x135b5f4> (NoMethodError) I just grabbed the

Hi Folks, I am glad to announce 1.0 release of BackgrounDRb. This would be a major release since 0.2 release of BackgrounDRb. Here is a brief summary of changes: - BackgrounDRb is DRb no longer. It makes use of EventDriven network programming library packet ( http://packet.googlecode.com ). - Since we moved to packet, many nasty thread issues, result hash corruption issues are totally

Howdy Folks- I''m happy to announce a new release of BackgrounDRb! I have added quite a few new features and included some nice patches from folks on the list. $ script/plugin install svn://rubyforge.org//var/svn/backgroundrb All of the code now stays within the plugin and the start and stop scripts are now just stubs. This makes it easier to tweak or figure out how it works.

Hi, Ok, As i promised.. I am working on new version of BackgrounDRB, which is getting close and will be out soon. I need some feedback from you guys. So, please reply back. The code has changed significantly and its no longer using DRB. But I will keep the name BackgroundRb. Ok, in new API, a worker looks like this: require "net/smtp" require "guid" class NewsletterWorker

Hey again, After playing with BackgrounDRb a bit longer, I have two more issues I''d like to bring up with it. 1. Logging... it seems like even when the environment is set to production in both Mongrel and the backgroundrb.yml file, all ActiveRecord SQL statements are written to the development log. If you''re doing a lot of ActiveRecord stuff in your workers, then the

Hi Folks, BackgrounDRb is a Ruby job server and scheduler. Its main intent is to be used with Ruby on Rails applications for offloading long-running tasks. Since a Rails application blocks while serving a request it is best to move long-running tasks off into a background process that is divorced from http request/response cycle. This new release of BackgrounDRb is also modular and can be used

This has been asked before, never well attended perhaps. Any thoughts on testing your workers? Current implementation is broken. An empty test case like this: require File.dirname(__FILE__) + ''/../test_helper'' require "#{RAILS_ROOT}/lib/workers/market_summary_worker" require "#{RAILS_ROOT}/vendor/plugins/backgroundrb/lib/backgroundrb.rb" require

Hi, just updated backgroundrb to release 1.0.1 and am getting this error when trying to start backgroundrb. vendor/plugins/backgroundrb/framework/core.rb:18: uninitialized constant Packet::ClassHelpers (NameError) Just updated from r298 where everything was working fine. If I comment out the offending line then backgroundrb starts but I can''t connect to it from my app. Anyone have any

Hi everyone, I noticed that script/backgroudrb requires config/environment which causes the backgroundrb server as well as the log worker to ''bloat'' to 35MB each. I am kind of sensitive to memory issues, so I patched the code and essentially moved the require of environment from script/backgroundrb to the meta_worker. Everything seems good and now both backgroundrb server and

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:

Hello, First off, nice improvements hemant! Thanks for all the hard work. I just whipped up a new worker for a scheduled job that sends digest emails. Very smooth. However, moving some of my old backgroundrb into new backgroundrb isn''t going quite as smoothly. I have a import worker that takes a number of parameters and then is started dynamically. Here''s the a

Hi Erza, I am using login engine in my code...and i get the error "uninitialized constant LoginEngine and uninitialized constant LoginEngine", when i try to do a find in the worker code!!! Why am i getting this error? -- nothing much to talk -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi, I would like to use backgroundrb inside a story, been trying to set this up for a while, but I think the only solution is to use fixture files and unit testing. The problem is that every time I call a new worker, the test database gets wiped out, and only has available the records in fixture files. Instead, it would be great if the test database maintains its state throughout the

I started emailing monit mailing list because I started getting this problem where I couldn''t start backgroundrb with monit anymore, thinking it was a monit problem. However, I back tracked a bit since I had added code to my project, and monit was able to start backgroundrb again. I seem to have zeroed in on the problem. I''m not sure where the problem lies - maybe monit or

Everything works fine on my development box (Ubuntu 7.10, Ruby 1.8.6) but on my server (Fedora Core 6, Ruby 1.8.5) when I run script/backgroundrb start, the process fails to start. This is with Rails 2.0.2 frozen in the app, and I have the most recent version of the plugin (r297). Is Ruby 1.8.6 a requirement for backgroundrb now? I can''t figure any other reason it would fail...