Fix is on my github; I've issued a pull request to the heroku user to
merge them into the official gem. Details here:
http://www.sarahmei.com/blog/?p=92
On Sun, May 24, 2009 at 10:53 AM, Sarah Mei sarah...@gmail.com wrote:
Ran into this yesterday. It's a bug in heroku client. I'm working on a
I am interested to switch to Heroku, but first I have some questions:
1. I will have a lot of assets (pics and videos) which I will be
storing in S3. Is there a bandwidth charge from Heroku to upload these
files to S3?
2. I am using thinking sphinx for database indexing. Is there a
restriction
I get this error for http://home-fogboundpictures.heroku.com/
Heroku | Backlog too deep
The application currently has too many requests in its backlog. If you
are the application owner, see http://docs.heroku.com/performance for
information on how to avoid this timeout.
That's fine, but when
This doc is in the works right now, thanks for giving us a friendly
nudge on getting it finished. :)
In the meantime, here's a rough cut of the explanation:
The backlog is the number of requests waiting to be processed. If
you're using the default (one dyno), it can only process one request
at
That was a good explanation and would make a good addition to the
docs. So what is the difference between a dyno and a compute unit?
Carl
On Mon, May 25, 2009 at 3:58 PM, Adam Wiggins a...@heroku.com wrote:
This doc is in the works right now, thanks for giving us a friendly
nudge on getting
@Sarah - you rock! Checking this out now, looking forward to pure-
windows heroku deploys.
On May 25, 2:21 am, Sarah Mei sarah...@gmail.com wrote:
Fix is on my github; I've issued a pull request to the heroku user to
merge them into the official gem. Details
