similar to: Invoker - 0.1.1 release, A gem for managing processes in development environment

Hello Folks, We just released Invoker version 1.2.0. Invoker is a pow alternative written in pure ruby that works on OSX and Linux. It is built on the idea of configuration over convention. Invoker can use a INI file or a standard Procfile as input and make your apps available on .dev domain and do bunch of other things. Code : https://github.com/code-mancers/invoker Docs and other information

Hello people, We have released invoicing gem which helps you in creating, managing and generating pdf for invoices. Bit of background: Invoicing gem was initially developed by Martin Kleppmann (https://github.com/ept/) for generating and displaying invoices. This release polishes the gem, makes it compatible with rails 3 and rails 4, adds pdf generation source:

Hello folks, I am happy to release version 1.0 of Invoker. Invoker is a utility belt for managing processes in development environment. Use it for managing multiple processes with ease. Use it for developing web applications on different local domains without /etc/hosts hacks. * Installation gem install invoker * Usage Invoker supports formean like process supervision and also makes http

Hi, Recently, we released a v.0.0.2 of our gem 'Rails-Legit'. This allows a clean interface to add validations for Arrays, Hashes and Time objects. Check it out at https://github.com/code-mancers/rails_legit. Do open an issue if anything breaks. Open to suggestions too! Thank you -- Kashyap www.codemancers.com -- You received this message because you are subscribed to the Google

Hi Folks, Troll trumps your existing ActiveResource mocking libraries like inbuilt HttpMock,Fakeweb or Webmock out of water. With Troll, ActiveResource mocking just works, some of its features: 1. Don''t need to mock calls at Net::HTTP level (which webmock,fakeweb do). Really, we don''t care what HTTP library ActiveResource uses, fakeweb and webmock bring additional complexity

hi, A new version of rapidfire gem (v1.2.0) is released Rapidfire gem makes adding dynamic surveys very easy in your rails application. source: https://github.com/code-mancers/rapidfire docs: http://rdoc.info/gems/rapidfire/frames demo: https://rapidfire.herokuapp.com Changes (v1.2.0) * Rails 4 is now supported * A new api is exposed to fetch survey results. It also

Hi guys, Today we released ministry_of_state - 0.1.0. This new version adds support for Rails 4. Code: https://github.com/code-mancers/ministry_of_state -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to

I have asked this before without any luck, trying again. this is what I have in my dj.rb initializer Delayed::Worker.backend = :active_record Delayed::Worker.logger = Rails.logger #Delayed::Worker.logger = ActiveSupport::BufferedLogger.new("log/ ##{Rails.env}_delayed_jobs.log", Rails.logger.level) class Delayed::Job def logger Delayed::Worker.logger end end if

Hi Folks, Well, Yesterday I pushed some more updates that I was cooking since last couple of days. Here is a brief list: 1. Results from worker stays even after a worker dies. 2. You can ask backgroundrb to store status objects in memcache cluster now. by default its stored in master process memory, but I have introduced an option to allow it to be stored in a memcache cluster:

Hi , If you are following commits, I have pushed following changes: 1. Now, you can specify :environment option in config file to load production environment and stuff. 2. Exeptions that were exposed to the user has been changed to BdrbConnError if rails is not able to connect to bdrb server. 3. loading mechanism has been changed, so remove backgroundrb script from your backgroundrb directory

Hi, I am pushing some updates and fixes that addresses much of the issues that we talked about since last couple of days. 1. Use configuration option :debug_log: false to disable backgroundrb_debug.log. 2. As shown below, use lazy_load option to disable aggressive loading of models ( and somewhat stupid too). 3. MiddleMan.delete_worker(:worker => :foo_worker) will now ABORT the worker, it

recently i noticed in my mongrel log files: /usr/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel/configurator.rb:374: [BUG] cross-thread violation on rb_thread_schedule() ruby 1.8.4 (2005-12-24) [i486-linux] any ideas why? With mongrel 1.0.1 -- gnufied ----------- There was only one Road; that it was like a great river: its springs were at every doorstep, and every path was its tributary.

Hi Folks, I am glad to announce a 1.0.1 release of BackgrounDRb library. It has numerous fixes and some nice feature updates, so please upgrade. Code: http://svn.devjavu.com/backgroundrb/tags/release-1.0.1/ Updates and Fixes: * Fixed issue with Mysql Lost connections * Message debugging can be disabled now with ''debug_log'' option in configuration file( :debug_log: false)

Hi Folks, Thanks for your patience, new release of BackgrounDRb is available now. You can get it from here: http://svn.devjavu.com/backgroundrb/trunk/ Yes, older version is deprecated and not supported anymore. A brief list of changes since last release is: 1. Now, each worker has logger objects, which can be used to log stuff. 2. A worker can be started or scheduled dynamically. 3. Multiple

1. Whenever you ask BackgrounDRb to perform a particular task using: MiddleMan.ask_work(:worker => :rss_worker,:worker_method => :fetch_url, :data => "www.google.com") Your task would be performed then and there. But, if your worker is busy, task won''t be queued, except in socket buffer. And your request may get lost. This isn''t generally a problem

Hey-- I''ve recently transitioned to the edge version of BackgrounDRb (2008-05-26) and I was curious what the opinion was as to the stability of it. Here''s been my experience with older and newer versions: Originally I was using revision 286 from subversion (back on 2007-12-17, I know I know it''s old) and it was working fine for development purposes, but I eventually

Folks, I have released a new verison of Packet(0.1.8), which has the fix for Mac OSX, please update your packet gem for getting the fix. Thanks. -- Let them talk of their oriental summer climes of everlasting conservatories; give me the privilege of making my own summer with my own coals. http://gnufied.org

Hi, 1. Is there any particular reason to not return ActiveResource objects when calling custom methods on Resources? Currently depending on request type, ARes returns hash or Net::HTTP::XXX responses. 2. I think know_attributes should be inheritable between ARes classes. Is there any reason to not do so? 3. custom methods can''t be directly overridden in plugins via modules, because

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

Hi All, One can easily code a backgroundrb worker so as it can act as a worker queue, having reached a stable status, perhaps its time we should add this feature. Why? Because if you are already running your application using BackgrounDRb, perhaps you don''t want to manage other solutions when capability to do that is right there with you. Interface? This where i need feedback. You can