On Wed, Mar 01, 2006 at 10:37:01AM -0600, David Heinemeier Hansson wrote: > So I added Kernel#daemonize yesterday thinking that I was going to > summon one for a book store application I've been getting real with, > but it did not go too well. Basically, as soon as I daemonize, I loose > the right to rely on auto-class instantiation and the database > connection is fuxored. > > Could anyone have a look at this? It'd be real swell if it was easy to > make daemons in Rails. > -- > David Heinemeier Hansson > http://www.loudthinking.com -- Broadcasting Brain > http://www.basecamphq.com -- Online project management > http://www.backpackit.com -- Personal information manager > http://www.rubyonrails.com -- Web-application framework > _______________________________________________ > Rails-core mailing list > Rails-core@lists.rubyonrails.org > http://lists.rubyonrails.org/mailman/listinfo/rails-core We've moved to creating drb instances which mirror our AWS api. These run well under a supervisor such as launchd, runit, daemontools, etc. All of our rails application instances (fastcgi listeners) are able to communicate through this for synchronization of, in our case, managed queues. I played with starting the Drb instance along with one of the fastcgi listeners, but too many issues came around to lead us to feel the separate and self-contained drb instance was a better solution in our case. -- TJ Vanderpoel GCIA,GCIH [EMAIL PROTECTED]
pgpf4BM72h8RX.pgp
Description: PGP signature
_______________________________________________ Rails-core mailing list Rails-core@lists.rubyonrails.org http://lists.rubyonrails.org/mailman/listinfo/rails-core
