Ok, so here's the deal. RailsCron is still available, but in the not_supported folder of my svn.
Why?
- RailsCron is threaded, which causes all kinds of nightmares when Rails isn't threadsafe.
- All of RailsCron's functionality is available in BackgroundRb (which is threaded too, ymmv).
- RailsCron's daemonization isn't terribly Capistrano-friendly
- 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.
Hello,
I am trying to install the daemon_generator plugin, but the link where the source is located is bad.
Posted by: Moses McCall | September 02, 2007 at 11:14 AM
i've tried the following:
ruby script/plugin install http://svn.kylemaxwell.com/rails_plugins/daemon_generator/trunk
but get the message "Plugin not found". anyone know if the path has changed and what it is now? thanks.
Posted by: Ryan | September 25, 2007 at 08:15 AM
I'm not sure if this is valid, but if you keep the TERM signal handling in your script, but end the script with "exit!" you don't get any errors.
Posted by: Richard Strand | October 17, 2007 at 02:57 AM