Shed a tear for a fallen hero. The loyal machine that hosted my previous blog died after 8 years of noble service. Welcome to WordPress, welcome to a new design and welcome to comments resist spam crusaders.
I’m looking for my pair of disk defibrillators to restore my previous posts and code. And I’m looking into hosting my previous SVN repository including responds_to_parent elsewhere. Google code? Rubyforge? Do you have any suggestions?
ak. the day i was looking to install responds to parent too : )
best of luck.
I second that (wanted to try out responds_to_parent also). I’d say that even though Rubyforge and Google Code don’t work 100% of the time for me, they should do the trick. Self-hosting SVN (and Trac!) is what I do.
Wow, popular day to try and install this plugin. Google code i suggest.
Google code looks like it’ll be a good place to start. I’d love to self host (again) but the overhead to administer Trac+SVN+OS is just beyond my pain threshold.
Hey Sean,
+1 for Google Code. It’s a fantastic place to host projects, track issues, etc.
Do you know where there is an updated version of
http://sean.treadway.info/articles/2005/07/18/upload-progress-checklist
?
It is linked from http://dev.rubyonrails.org/browser/plugins/upload_progress/README
What happened to your upload_progress plugin? I thought it worked rather nicely at the time.
Stephan
Ohh, the upload_progress plugin is now in the Rails plugins repository. It was mostly proof of concept that one could do magical things with Rails and Ruby, but in any kind of concurrent environment, the progress checking shouldn’t be in an application server process.
The server requirements that were supposed to roll in as people tested the plugin were very disappointing, namely the only configuration that worked most of the time was Apache 1.3 + FCGI, specifically turning off FCGI buffering in the apache config and tuning the Apache request duration timeouts. The Ruby/C FCGI adapter also revealed some bugs on FreeBSD.
I’d recommend to not do progress checking with a heavyweight Rails process. 80-100MB is too much for a single upload connection that will block all other requests to that app instance. Setting up a dedicated mongrel server to handle the uploads would be the best route to go to stay within the ruby world.
http://mongrel.rubyforge.org/wiki/UploadProgress