Every Student

Where did form_remote_upload go?

Well, it may not be completely intuitive by the name, but the official upload_progress plugin contains the functionality of form_remote_upload (that is, AJAX file uploads). Check it out at:

http://dev.rubyonrails.org/svn/rails/plugins/upload_progress/

RailsCron Deprecation

Ok, so here's the deal. RailsCron is still available, but in the not_supported folder of my svn.

Why?

1. RailsCron is threaded, which causes all kinds of nightmares when Rails isn't threadsafe.
2. All of RailsCron's functionality is available in BackgroundRb (which is threaded too, ymmv).
3. RailsCron's daemonization isn't terribly Capistrano-friendly
4. I wrote daemon_generator, which allows you to easily incorporate your own daemons into Rails. It's minimal, and it's what I actually use. Focusing on the daemons, without coupling messaging and database dependence, is the way to go for me.

If you want bare-bones, stable, and functional, use daemon_generator. If you want messaging and features, use backgroundRb. I don't see value in RailsCron anymore.

Announcing daemon_generator

After writing rails_cron, and working with backgroundrb, I realized that I want something simpler. Much simpler. So I wrote the daemon_generator plugin. I think the whole thing is about 50 lines of code.

"./script/generate daemon <name>" gives you a simple stub that you can dump code in that will run in the rails environment as a background process. You're responsible for making it do something useful (try accessing stored tasks in a memcache or DB-based queue). If you want messaging, try backgroundrb.

Features:

• Capistrano-friendly i.e.:
  

  task :after_restart do
    run "#{current_path}/script/daemons restart"
  end



• Per-daemon start scripts


• Per-app start scripts


• Graceful stop and restart


• Per-daemon logging in your log folder


• Automatic restart of a crashed daemon


• Not thread-based

Go get the plugin:
daemon_generator 0.5.0 | README