% heroku rake db:migrate --trace
rake aborted!
LoadError: no such file to load -- sequel/adapters/postgresql
In my Gemfile,
gem 'pg'
gem 'sequel'
The app runs on local machine.
Any help is much appreciated.
--
You received this message because you are subscribed to the Google Groups
"Heroku"
>From support:
"Sorry for the delayed response. We've had some issues with convergence that
was preventing workers to get restarted properly. We've resolved them. The
last crash I see is 4:33 and they've stayed running since."
On Tue, May 24, 2011 at 8:05 AM, nevinera wrote:
> It is most li
Thanks, didn't think of that.
On Tue, May 24, 2011 at 12:39 PM, Steve Smith wrote:
> Why not add the free version of new relic and then you can see they wait
> queue as part of the output.
>
> Steve
>
> On 24 May 2011, at 18:38, iamtheschmitzer
> wrote:
>
> I just increased my customers signifi
Why not add the free version of new relic and then you can see they wait queue
as part of the output.
Steve
On 24 May 2011, at 18:38, iamtheschmitzer wrote:
> I just increased my customers significantly (yay), but saw for the first time
>
> Error H11 (Backlog too deep)
>
> so I added a seco
I just increased my customers significantly (yay), but saw for the first
time
*Error H11 (Backlog too deep)*
so I added a second dyno. I had been watching the logs for delays:
*dyno=web.1 queue=0 wait=0ms service=4ms bytes=3202
*
looking for non-zero wait or queue ahead of the Backlog too de
If your process is terminating too often, Heroku will start leaving
longer gaps between attempts to start it. You might try collecting the
logs for your worker processes and seeing if there's anything
interesting to be gleaned from that.
heroku logs --ps worker
-p
On Tue, May 24, 2011 at 5:05 AM
We would like to use CarrierWave for handling our uploads on Heroku,
but it needs to cache locally to the /tmp directory. I am concerned
that if many users are uploading at once, the directory could fill up
and hit the maximum disk size limit imposed by Heroku.
Is there a way to upload directly t
It is most likely not a platform problem, though you can assume what you
like.
Heroku workers are just calls to `rake jobs:work` from your app, and a
watchdog that calls it again if the process dies - not much to go wrong
there really.
--
You received this message because you are subscribed
If you if you set your cache headers properly, for something like a
blog, you can easily scale up to a huge number of visitors.
Cache hits are free and fast with Heroku's Varnish layer.
Alex
On May 23, 11:15 pm, "Mike P." wrote:
> Hi all,
>
> I was wondering how you all are handling your blogs
