On Wed, Dec 3, 2014 at 3:34 PM, Harisankar P S <[email protected]> wrote:
> > You could use the sucker punch gem which does the background processing > along with the rails process, so there shouldn't be the need to start > another dyno. Not sure about if we can schedule it to start at a particular > point of time. > > > http://brandonhilkert.com/blog/why-i-wrote-the-sucker-punch-gem/ > > Thanks..this seems to be a suitable gem for my purpose. The resque / resque-scheduler was overkill since it was costing $70 a month just to run simple scheduled tasks . > Btw, just curious. Cant we write cron jobs in heroku? Using something like > the whenever <https://github.com/javan/whenever> gem. > I am not sure conventional cron jobs can be made to work on heroku. There is no persistent file storage so even if the crontab file is edited, it wont reflect on any other dyno. Thanks, Ganesh -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/CALFmRoGKEwBjzr1JE%2BYWd3s0Vahjz%3DXeZxx4WZpsbThoYs8WGg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
