similar to: mongrel_upload_progress + upload.rb +background (daemon?)

I have noticed that occasionally (about 50% of the time) when i deploy (using capistrano) my app to a production server, i have to ssh into the box and manually stop and start backgroundrb to get it to load my workers. this is my basic setup i have 2 workers: lib/workers/mp3_worker.rb => takes a hash of params to downsample an mp3 lib/workers/flv_worker.rb => takes a has of

ok, i was wrong. the failure on deployment using capistrano is 100% using these commands ## Our Handlers desc "Restart BackgrounDrb" task :restart_uploader, :roles => :app do run "#{current_path}/script/backgroundrb stop" run "#{current_path}/script/backgroundrb start" end here is the console post deploy on the remote server ######## [current]$

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.

I just got the mongrel_upload_progress set up with drb and the setup was quick and easy, thanks to the good documentation on http://mongrel.rubyforge.org/docs/upload_progress.html I''d like to get this set up with capistrano, but there are 3 things I can''t figure out: - First, I can''t get lib/upload.rb to run in the background - I''m not familiar with

i get this: undefined method `object'' for nil:NilClass when i try to get the status of a worker after backgroundrb 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.

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?

Can one use mongrel_upload_progress in combination with attachment_fu (db_file)? I wan''t to store uploaded files directly in a mysql-database - not in the filesystem. Is there a way to use mongrel_upload_progress to do this, or do I have to store files in the filesystem and copy them to the database? Thanx

What is the status of the mongrel_upload_progress gem and Rails? I have been playing around with _why and technoweenie''s code but I''m not sure what is current and what is old. It is not working for me. I am running Mongrel 0.3.13.3 (gem) with mongrel_upload_progress 0.1. My upload URI is /agronomics/sample_cycle/upload, and my progress URI is

G''day I''m just wondering if anybody knows of a way to get mongrel_upload_progress working with nginx? I''ve had a fair bit of a look around but havn''t been able to come up with anything, yet. -- - James -------------- next part -------------- An HTML attachment was scrubbed... URL:

I started actually using the upload progress handler, and noticed it was leaking memory over time. Looking at the code, I noticed that cancelled uploads weren''t being cleaned up. I bugged Zed about adding a request_abort callback to handlers, but I found a simple way to monkey patch that in: # config/mongrel_upload_progress.conf # yes, this file is being used with -S meaning

Hello, So, I grabbed the mongrel_upload_progress code from subversion because I really need something similar for a project I am working on. Anyway, I installed the gem and can''t figure out a few things. 1) I''m not sure what Upload < GemPlugin::Plugin "/handlers" is for 2) How to call the Progress < GemPlugin::Plugin "/handlers" handler. While I

Hi, I wrote a message earlier regarding how I wasn''t getting any feedback from mongrel_upload_progress. After putting lots of debug messages in the plugin, I figured out what was going on. I had a route like this setup in routes.rb (this was the problem): map.upload "upload/:upload_id", :controller => "file", :action

I''m a bit confused about how to get upload progress to work with mongrel.. I''ve installed the mongrel_upload_progress (0.1) gem, but have no idea what to do with it. According to the following page: http://technoweenie.backpackit.com/pub/602283 there''s a patch (mup.diff) which seems like it patches the mongrel_upload_progress plugin The following blog entry makes it

Hi guys, I had mongrel_upload_progress working very sweetly on my dev machine, where mongrel was acting directly as the webserver. But when I went to production it stopped working. The Problem: On our production server we use Lighttpd, and it looks like lighty is buffering the whole upload and then giving it to Mongrel in a big chunk. This pretty much screws up the whole point of

I have Mongrel 0.3.13.4 running Rails 1.1.6 behind Apache 2.2.3 with mod_proxy_balancer, mongrel_cluster 0.2.0 as per the documentation, and mongrel_upload_progress 0.2, on Fedora Core 4. I''m using a cluster of three Mongrels. I have an existing app which allows users to upload files, and I''m migrating it to Mongrel from Lighttpd. Uploading files via multipart forms

Hi, Just trying to get Capistrano working to Dreamhost. I''m hitting a permissions issue on the reaper file at the moment. Has anyone a copy of the capistrano DEPLOY.RB file they could post or send me a copy of please? Thanks Greg -- Posted via http://www.ruby-forum.com/.

Like most people, I find the file upload process very annoying, in that you hit submit and sit there, seemingly forever, as your file gets sent. So I felt it would be a great goodness to have progress updates as file_upload_progress offers. However, I have been unable to get it to work, and I''m not sure why. I created the form roughly as said, except that my target is

Hi Is there some definitive guide for upload progress plugin ? We have in this mailing list a lot of testimonials, bug reports, bug fixes, but there are still people like me who cannot use it correctly. Here is my config: - mongrel 1.0RC and upload progress plugin 0.2.1 - a 6 mongrels cluster - config/mongrel_upload_progress.conf: uri "/", :handler =>

I am trying to get the mongrel upload progress working and am having some problems. I am using Rails 1.1.6 and the latest install of mongrel. I created the config/mongrel_upload_progress.conf per the instructions ... it looks like this ... uri "/", :handler => plugin("/handlers/upload", :path_info => ''/listings/ add_photo''), :frequency

Hi, I have a mongrel cluster with a mongrel_upload_progress ... when I upload a file, my cookie session id changes .... So on the upload form, my Session ID is say: BAh7ByIKZmxhc2hJQzonQWN0aW9uQ29udHJvbGxlcjo6Rmxhc2g6OkZsYXNo%0ASGFzaHsABjoKQHVzZWR7ADoOcmV0dXJuX3RvIj8vdXBsb2FkL25vdz91cGxv%0AYWRfaWQ9M2Q0MzJiN2UtYWUxYy0xMWRjLTgzNDEtMDAxNTE3NGE0NDVj--9a36dd5853f963386ba042995bf66630c0b5734f And