Heroku supports hourly cron jobs. if that's not often enough, and you have a cheap shell account somewhere else, you can set up a cron job there that every 30 seconds does a wget to a URL in your heroku app; if you put the background tasks into a table, then you will have a poor man's work queue. Not ideal, but it will tide you over until Delayed Jobs becomes stable and widely available.
On Fri, Apr 24, 2009 at 9:44 AM, Felix Holmgren <[email protected]>wrote: > > Hi everyone. I'm thinking of developing a project specifically for > deployment on Heroku, and would appreciate some advice from the > community and staff. > > The app is basically an RSS collector with a web service API to be > consumed by clients. I want to use Sinatra for the web service. > > However, by the nature of this app, I need to run background processes > more or less constantly. I had problems deploying a Rails app with > background processing earlier, and had to move it back to my old > server, but I'd really like to make this work with Heroku. > > I see Delayed Job is in beta. How can I try it out? And any hints > about when Workling might become available? > > Also, does anyone have advice on whether using these background job > frameworks is really the best way of structuring an app like this. > Perhaps it would be better to just have the RSS collector running as a > separate app? Is it possible to have two apps on the cloud share a > data base? > > Any advice would be ridiculously appreciated! > > /Felix > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
