On Sat, May 08, 2010 at 04:01:51PM -0700, Kandada Boggu wrote:
> I have a rails application running on Heroku. I want to use Ruote for
> implementing a long running business process. I am thinking about
> using RuoteKit, an DataMapper(for persistence).
> 
>   1) Has anybody deployed Ruote on Heroku? Did you encounter any
> issues?
>   2) How are engine/worker(s) configured. Who is running the worker?

Hello Kandada,

I have a rack application deployed on Heroku :

  http://github.com/jmettraux/barley

It used to run at :

  http://freezing-stone-20.heroku.com/

But since a month or two it's in "Oops, we seem to have a glitch in our 
system." mode. I have had no time to investigate. I should probably try to 
install/re-install the app. If I have to help you, I will have to do it anyway.

It's using Ruote::Dm::DmStorage.

The worker is running inside of the engine.

  http://github.com/jmettraux/barley/blob/master/barley.rb#L71-74

It's easy to infer from that example what a ruote-kit system would look like.


Now on to the specifics of the platform.

If you don't use the "wait" expression and timeouts, all is well.

When such schedules are involved, you can't trust Heroku. After a period of 
inactivity, the process running your app and the ruote worker inside it will 
shutdown until a new request comes and the process is brought back alive (a new 
process that is). At this point schedules will wake up.

That means that if a wait expression is meant to resume in a process at 4pm and 
the system is still from 2pm to 5pm, the wait will resume at 5pm (when there is 
a worker back).

For some processes a granularity of 1 day is OK, for others not, you are the 
judge.

If you need a better granularity, you unlock the (paying) hourly cron add-on 
and let heroku "tease" your app and ruote inside it once per hour.

If you need help with that, please tell me.


Best regards,

-- 
John Mettraux - http://jmettraux.wordpress.com

-- 
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

Reply via email to