similar to: Picolena, a ferret+rails documents search engine

I can''t get to the code anymore. Devjavu''s svn is asking for a username and password. http://svn.devjavu.com/backgroundrb/ Authorization Required This server could not verify that you are authorized to access the document requested. Either you supplied the wrong credentials (e.g., bad password), or your browser doesn''t understand how to supply the credentials

Hi devs, I was trying to open a new ticket with a minor doc patch at the BackgroundDrb Trac (http://backgroundrb.devjavu.com/) and it seems like only admins have permission to do so. Is this intended? I read in the readme that patches should be mailed to this list, but I much prefer to use Trac since there''s already one set up. Any reason Trac is not open to registered Devjavu users?

Sorry for attaching patches in emails to the mailing list, but I''m still unable to login to Devjavu for Backgroundrb (I''m able to login just fine for Merb''s Devjavu and submitted a ticket successfully). Anyway, I encountered a bug when trying to #ask_status of a worker before it''s run (or rather, before its result_hash has been set to something). Not sure why

#set_status http://merb.devjavu.com/browser/trunk/lib/merb/mixins/render.rb#L270 refers to a non-existent constant. I tried, while creating #359, to make things OK, but I failed. I started by using STATUS_CODES instead, then used #[] instead of calling a method named STATUS_CODES, then I found out that during the call to #inherited

Objective: All web traffic originating from my proxy server should be forwarded through interface eth2 instead of the default eth0. The reply should take the same path back to the proxy server. Problem: On the return bout, the kernel doesn''t pass the packet to the higher layers. The reply seems to be getting tossed away between PREROUTING and INPUT Netfilter chains.

Hello Folks- I am really happy to announce the release of BackgrounDRb 0.2.0 . This is a complete rewrite and re-architecture of this codebase. I want to thank skaar for all of his hard work. I put out a call for help with the new architecture and skaar stepped up bigtime. I had already written the new scheduler and cron compatible syntax and moved to multi process architecture. But he

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

Since this morning, the server at http://svn.devjavu.com/backgroundrb is requiring authorized access. Could you guys look into it? Thanks, Saimon -- Saimon Moore Freelance Web Developer (Available for hire - For details visit http://saimonmoore.net) Skype: saimonmoore Yahoo IM: saimonmoore Google IM: saimonmoore

Hello, I''ve been trying to get the latest copy of BackgrounDRB as per the documentation here http://backgroundrb.rubyforge.org/. However, whenever I try to access http://svn.devjavu.com/backgroundrb/tags/release-0.2.1 I keep an authentication prompt and if I leave it blank I am declined access. Is there somewhere else to get the code or am I doing something wrong? Thanks, -carl --

Is it really a hash? As in, can I pass it into a method that a worker is calling so that, for example, a method in my ActiveRecord that''s actually doing the work? Really liking the new code. Does rubyforge or devjavu have the rdocs anywhere? -- Joshua Warchol Code Poet, Zaadz Inc. http://joshua.zaadz.com/

Hi, I''ve started looking at ticket 90<http://merb.devjavu.com/projects/merb/ticket/90>and there are a couple of situations that the current implementation doesn''t cater for. 1. Tag Attributes are wiped out. - <tag1 attr1=''1''>Content</tag1> #=> { "tag1" => "Content" } - I think it should return -

Following up on #190 [1], I''ve just added a simple patch that allows the manipulation of the TYPES hash from within the Merb module. Use like: Merb.add_mime_type(:png,%w[image/png]) Merb.remove_mime_type(:png) It specifically disallows the removal of the :all MimeType, since content negotiation relies on it. I''m not super wonderful at API design, so comments and

I''ll probably do my respond_to API rewrite, as discussed here: http://rubyforge.org/pipermail/merb-devel/2007-September/000275.html sometime this week, unless someone has come up with a better API. I''ll also work in http://merb.devjavu.com/ticket/227 at the same time. Any serious objections?

After upgrading to backgroundrb 0.2.x, Rails barfs lstat errors left and right when using the console or webrick or mongrel on win32. We run our site on a Linux server, so I''m not trying to get backgroundrb to work on a win32 machine. I just want to quietly stop loading itself if it detects that it''s on a win32 machine so that the rest of Rails can continue to load. Most of

The http://merbivore.com/get_merb.html#trunk page mentions the 0.4.0 version, but 0.4.1 is out. Is this a part of the site which will be constantly updated as part of the release cycle? The roadmap on merb.devjavu.com has outstanding tickets for 0.4.0 and 0.4.1, yet both versions are out. Were those issues fixed, or should they be bumped forward? Yeah, this is really anal crap, I know. I would

So, what''s the status of this project? I''m a little confused. The documentation at http://backgroundrb.rubyforge.org seems out of date. It refers to http://svn.devjavu.com/backgroundrb/tags/release-0.2.1, which doesn''t work. All I want is a way to easily set up tasks that should run periodically. Some stuff should run every 10 seconds, some stuff once a day, etc.

Ok two things that bug me 1) http://backgroundrb.devjavu.com/projects/backgroundrb/ticket/48 i thought i''ll just post ticket link - but well - it''s strange 2) when i switch base class from RailsBase to Base i can''t access MiddleMan - i get error NameError: uninitialized constant MiddleMan from (drbunix:///tmp/backgroundrbunix_localhost_2999)

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

Hi everyone, I''m new to backgroundrb, and I''m trying to get started with a simple example, yet with no success. This is the code that I have in RAILS_ROOT/lib/workers/testing_worker.rb class TestingWorker < BackgrounDRb::Worker::RailsBase def do_work(args) # This method is called in it''s own new thread when you # call new worker. args is set

I''ve submitted a few patches on Trac to help get Merb running under JRuby [0][1][2][3][4]. It''d be cool if any of you committers could find the time to look them over and apply/reject them. They''re mostly tiny, so it shouldn''t be too onerous. With all of these patches applied, there are still 3 spec failures. One is in the spec ''a merb mailer