Interesting. Does using Heroku pre boot also achieve this or does the 60 second limit still apply? https://devcenter.heroku.com/articles/labs-preboot/ What happens to requests that get routed to the 'live' dyno before the app has started?
-- Neil On Thursday, 13 December 2012 at 15:21, Daniel Doubrovkine wrote: > Many have been struggling with the Heroku R10 boot timeout. > > Announcing heroku-forward, a new gem for those with larger or slower > applications struggling to boot on Heroku within the 60s timeout limit. See > http://artsy.github.com/blog/2012/12/13/beat-heroku-60-seconds-application-boot-timeout-with-a-proxy > for an introduction. > > Of course, it's best not to have this problem and being able to boot your > application in less than 60 seconds, but this could be your short/medium term > fix when you hit the boot time limit. > > Hope it helps, > > cheers > dB. > > -- > dB. | Moscow - Geneva - Seattle - New York > dblock.org (http://www.dblock.org) - @dblockdotorg > (http://twitter.com/#!/dblockdotorg) > -- > You received this message because you are subscribed to the Google > Groups "Heroku" group. > > To unsubscribe from this group, send email to > heroku+unsubscr...@googlegroups.com > (mailto:heroku+unsubscr...@googlegroups.com) > For more options, visit this group at > http://groups.google.com/group/heroku?hl=en_US?hl=en -- You received this message because you are subscribed to the Google Groups "Heroku" group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en
