When we first launched we ran into the 30 second heroku timeout issue that was a... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		PStamatiou on May 30, 2012 \| parent \| context \| favorite \| on: Picplum Tech Stack - Backbone, Async Uploads, Prin... When we first launched we ran into the 30 second heroku timeout issue that was affecting us with some users and larger uploads. The easiest option was just dropping in the Transloadit endpoint. We have a dedicated EC2 instance that we have been planning on converting to our upload box with nginx and its upload module.

robryan on May 30, 2012 [–]

Interesting reading that and after reading: http://icelab.com.au/articles/money-stress-and-the-cloud/ (tl;dr: Credit card processing was breaking because of the 30 second limit).

Sounds like it would make sense for heroku to have a configurable timeout.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact