The typical way to do stuff like that is to write a rake task that you
run at the command line (or via cron), but I'm new to Heroku and I'm
not sure how they handle the running of custom tasks. I'll leave that
to the Heroku experts. :) HTH.

On Thu, Apr 17, 2008 at 6:46 PM, cmk <[EMAIL PROTECTED]> wrote:
>
>  I'm a long time developer but new to ruby, rails, heroku, and, in
>  fact, web applications in general.  I'm trying to create a background
>  process to do tasks outside the normal request/response cycle. [...]

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

Reply via email to