Ruote-kit gives option to define a worker outside of rails app. In its
"running workers" at *https://github.com/kennethkalmer/ruote-kit, it says:
*
To run a worker you need to setup a worker script similar to the rake
task example below:
require 'rake' require 'ruote-kit'
desc "Run a ruote-kit worker" task :ruote_kit_worker do
RuoteKit.run_worker(Ruote::FsStorage.new('ruote_work')) end
There is a ruote.rake of above which is automatically saved into lib/tasks.
Since there is NO worker instantiated
in rails initialization and we know ruote engine needs at least one worker
running at any time:
1. when and how (by Rake::Task['ruote'].invoke in rails app?) in rails app,
ruote.rake should be called to instantiate a worker?
Or worker only needs to be instantiated once for the rails app.
(For worker within a ruote engine, worker is created in rails initializers
along with ruote engine).
2. Does rails app need to kill the worker after the required data processing is
done? Or just leave it running for next request.
3. In which situation does rails app need more than one worker instance?
Thanks for help!
--
--
you received this message because you are subscribed to the "ruote users" group.
to post : send email to [email protected]
to unsubscribe : send email to [email protected]
more options : http://groups.google.com/group/openwferu-users?hl=en
---
You received this message because you are subscribed to the Google Groups
"ruote" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
