A Heroku worker is essentially this: If you create a process in your app that is started by running "rake jobs:work" we will keep it running. If you want to consume the Twitter firehose with that process, it should work great. You can also use DJ, Resque, etc as your implementation of "rake jobs:work"
On Dec 8, 2010, at 3:02 AM, jurglic wrote: > Hello Guys, > > This is a very interesting topic, I'd also like to know more about it. > > I was quite sure this wouldn't work, because you probably don't have > rights to start off a deamon in a worker. Has anyone tried it yet? Or > maybe any official answer from Heroku Team? > > I was thinking of using something like that for Twitter Firehose API, > because otherwise I really don't know any way to consume twitter feed > in realtime on Heroku.. > > > Cheers, Uros > > On 8 dec., 08:09, Chris Hanks <[email protected]> wrote: >> Well, since you pay for workers by the hour, I'm sure Heroku would be >> perfectly happy with you keeping many of them busy for a very long >> time. >> >> On Dec 7, 10:44 pm, Jonas <[email protected]> wrote: >> >>> Nice. So that was actually what I initially thought. >>> And there is no limitation on what that worker does? I mean, it's okay >>> to preoccupy that worker till eternity? :) >> >>> On 7 Dec., 20:53, David Dollar <[email protected]> wrote: >> >>>> A Heroku worker is simply running "rake jobs:work" on your app so whatever >>>> happens behind that rake task is up to your app. >> >>>> On Dec 7, 2010, at 10:47 AM, Jonas <[email protected]> wrote: >> >>>>> Hi guys, >> >>>>> Hi guys, >> >>>>> Ok, so I've succesfully developed a daemon that fires up EventMachine, >>>>> subscribe to a data feed and communicate that data to Pusherapp.com >> >>>>> Everything is working beautifully in production on my OSX development >>>>> machine, and now I want to deploy to Heroku. My initial understanding >>>>> was that the Heroku workers would suite this purpose well, however >>>>> I've come to realize that I might be wrong. >> >>>>> My question is, how do I run a daemon in the Heroku environment? >> >>>>> Some facts: >> >>>>> Ruby 1.9.2 >>>>> bamboo-mri-1.9.2 (beta) >>>>> Rails3 >>>>> Daemons gem:https://rubygems.org/gems/daemons >>>>> The deamon_generator plugin:https://github.com/dougal/daemon_generator >>>>> An old Railscast that describes approx. how a daemon like this is set >>>>> up:http://railscasts.com/episodes/129-custom-daemon >> >>>>> How the daemon works: >>>>> I've setup a rake task to start the daemon, briefly, this is the >>>>> process: >>>>> 1. Rake task calls "lib/daemons/my_daemon_ctl start" >>>>> 2. Require some gems and start daemon: Daemons.run >>>>> File.dirname(__FILE__) + "/my_daemon.rb", options >>>>> 3. Loads rails env and starts the EventMachine reactor: >>>>> EventMachine::run { data feed and pusherapp black magic here } >> >>>>> -- >>>>> You received this message because you are subscribed to the Google Groups >>>>> "Heroku" group. >>>>> To post to this group, send email to [email protected]. >>>>> To unsubscribe from this group, send email to >>>>> [email protected]. >>>>> For more options, visit this group >>>>> athttp://groups.google.com/group/heroku?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "Heroku" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/heroku?hl=en. > -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
