That's how Heroku works -
http://docs.heroku.com/performance#request-timeout. A console command
is treated identically to a HTTP request.
Oren
On Sun, Aug 1, 2010 at 6:57 PM, Mike wrote:
> Okay, actually fixed this, sort of, by updating my heroku gem.
>
> Now it now longer crashes and just quit
Okay, actually fixed this, sort of, by updating my heroku gem.
Now it now longer crashes and just quits the console and tells me that
it's timed out and I should run it as a rake task instead of from the
console.
Overall behavior seems to be the same still, with the request
continuing to run on t
I'm updating some data in my database, and running them through the
Heroku console since we have no direct database access.
I'm calling this like so: ActiveRecord::Base.connection.execute "MY
SQL COMMAND;"
The command takes about 5-10 minutes to run.
Every time I run it, it's causing the console
On Tuesday August 3rd we will be updating Bundler to 1.0.0RC2. Apps
will continue to run unaffected. Before you push an update, please
double check that your app works correctly with the latest version of Bundler.
Some things to note:
* Adding an add-on or a config var will recompile your appl
I know heroku is probably just evaluating the RC, but I'd love to see
it soon as well.
On Jul 29, 2:41 am, Eric Hurst wrote:
> > Will Heroku be upgrading to that version of Bundler? I'm not sure how
> > to test our Rails 3 on Heroku otherwise.
>
> +1 for Bundler RC support.
--
You received this
