search for: indierockmedia

...lts. how would i go about ensuring that when i deploy that backgroundrb restarts properly? ideally i will only be restarting backgroundrb when i have model changes or worker class changes that would affect it''s operation. Jerrod Blavos ph. 919.341.0143 fx. 482.492.5009 jerrod at indierockmedia.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/backgroundrb-devel/attachments/20070205/1463d282/attachment-0001.html

so i have an after_create method on my track model that kicks off a background process that converts an mp3 to a swf. this is working fine locally on my machine, but upon moving it to my production server, i am getting the following error. I''ve only been using backgroundRB for like 48 hours, so i''m not really sure what this means or where to go. any ideas?

...sc "Restart BackgrounDrb" task :restart_backgroundrb, :roles => :app do run "cd #{current_path} && script/backgroundrb stop" run "cd #{current_path} && script/backgroundrb start" end Jerrod Blavos ph. 919.341.0143 fx. 482.492.5009 jerrod at indierockmedia.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/backgroundrb-devel/attachments/20070205/44e360df/attachment-0001.html

...drb has been restarted using a job key saved in the DB. how do i get around this? i know the process is nonexistent, but shouldnt it return something more friendly if it doesnt exist? am i forgetting something? Thanks! -Jerrod Jerrod Blavos ph. 919.341.0143 fx. 482.492.5009 jerrod at indierockmedia.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/backgroundrb-devel/attachments/20061219/703c9598/attachment.html

is it possible to use these together? im asking because in the sample docs for mongrel_upload_progress, it has you start by hand a druby instance. This doesnt work very well when moving to production. as in, i cant seem to get that particular process to either stop or restart after a new deploy. I posted to the mongrel-users list about this and have not gotten any sort of response.

Im checking out the mongrel_upload_progress plugin and have it working beautifully on my dev box. however, now that i am ready to push this up into production i have run into a few gotchas that i cannot seem to find any documentation or examples for. the lib/upload.rb doesnt seem to want to run in the background. perhaps im doing something wrong? Does anyone have any experience