similar to: mongrel_cluster + mongrel_upload_progress + drb + capistrano + docs

Hi all, I''m using Boxroom (http://boxroom.rubyforge.org/) and trying to get upload progress working. I''ve also been testing the sample code at http://itblog.mcgeecorp.com/2007/5/15/mongrel-upload-progress-demo/. I run a Mongrel cluster, and so am using drb (as per http://mongrel.rubyforge.org/docs/upload_progress.html). Starting up rails, I get lots of useful-sounding output:

Hey y''all: mongrel_cluster provides management tools for running Mongrel behind a reverse-proxy/load balancer. It is an extraction from Rails Machine, a deployment service and Ruby library that simplifies Rails application deployment. This release fixes bugs and adds a Capistrano task library. Changes: -changed pid file format to include port -only write configuration options

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

Hi Guys, I hope its ok to post to this list. I have a rails on ubuntu deployment stack which consists of: locally: cap 2.3.0 and all latest deps server side: apache 2.3, mongrel_cluster, mod_proxy and git on the same host. I am connecting to my remote host via ssh with agent and pass phrase. All is good until my first mongrel task, deploy:restart task. I have included the

Ok, So I''m running mongrel_cluster behind a hardware load balancer. I don''t have apache running at all, just mongrel_cluster. Does anyone know how I can get cap disable_web/enable_web to work without Apache. With no apache I can''t just make an .htaccess file change like the docs state. has anyone rewritten disable_web/enable_web to work with just mongrel_cluster and

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

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:

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

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 mongrel users! I just posted a bad-ass capistrano file that automates *everything* for setting up an apache2+mod_proxy_balancer and mongrel+mongrel_cluster -- including apache2 setups. It''s based off Coda Hale''s guide and all Bradley''s work at fluxura and RailsMachine (thanks Coda and Bradley!). It''s, well, bad-ass, if I must say so myself. My favorite

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

Whenever I tried to start mongrel_rails with the upload progress script, it would die with the following error: /usr/local/lib/ruby/1.8/drb/drb.rb:837:in `getaddrinfo'': getaddrinfo: No address associated with nodename (SocketError) from /usr/local/lib/ruby/1.8/drb/drb.rb:837:in `open_server_inaddr_any'' from /usr/local/lib/ruby/1.8/drb/drb.rb:860:in

I posted this to the rails list before by mistake, and only later realized that there is a specific mongrel list. Uff, I got lost. I had mongrel_cluster 0.1working fine, even with capistrano (my own hack). Then came mongrel_cluster 0.1.1 and I tried to set it up, but somehow I messed up things and nothing worked anymore. So here is what I did: on production machine: (debian linux, rails 1.1)

Hi there, I''m using Mongrel (0.3.13 prerelease, installed today) to serve up some Rails apps in production. Everything works fine if I give all the appropriate options on the command line, such as: $ mongrel_rails start -c /home/mcornick/rails/mcornick.org/current -P log/mongrel.pid -l log/mongrel.log -e production -d -a 127.0.0.1 -p 6833 So, having accomplished that, I thought it

Hello! Run problems after upgrading to mongrel 1.0.3 from 1.0.1: # uname -sr FreeBSD 7.0-BETA1 # mongrel_rails start ** Starting Mongrel listening at :3000 ** Starting Rails with development environment... ** Rails loaded. ** Loading any Rails specific GemPlugins ** Signals ready. TERM => stop. USR2 => restart. INT => stop (no restart). ** Rails signals registered. HUP => reload

Hey all, First off, thanks to Rick Olson and whoever else was involved with this plugin... It''s been amazingly easy to implement. I''ve got a question about the path_info parameter, though... It seems that unless the request PATH_INFO exactly matches the path_info passed in to the plugin at inclusion, it won''t actually trigger Add and add the upload to the list of

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''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