FYI, I solved my problem using psionides' Resque (with multi-json
support); though workers goes on only with ruby 1.8.7 and not 1.9.2.
http://github.com/psionides/resque/
Thanks,
Clément
On Oct 4, 8:32 pm, James Bracy ja...@redistogo.com wrote:
Clément,
Looks like something is up with the
Thanks for looking into this stuff, Ben.
On Oct 5, 11:33 am, Thomas Balthazar gro...@suitmymind.com wrote:
Hello Ben,
I just read you were about to talk to the Varnish specialist at Heroku.
I would really appreciate if you took the time to help me to find the
answer to those 2 unanswered
Anyone here have any experience with long running rake tasks on
Heroku?
From the Heroku documentation, it seems like when you have long
running processes, that rake tasks are the recommended way to handle
them. However, in my experience, whenever a rake task runs for a
while, say around 30
I have a background job running as a worker that needs to generate and
write large files to s3.
From what I can tell s3 doesn't support chunked transfer encoding so I
need to know the size of the file before I can start writing it to s3.
One option is to write the file to memory before putting to
The file size limit is in the many gigs range. Clean up after
yourself and you shouldn't have any problems.
Workers are capped at the same memory limit.
Oren
On Tue, Oct 5, 2010 at 7:11 PM, mdgbayly martin.ba...@gmail.com wrote:
I have a background job running as a worker that needs to
In just manual testing my app, I've seen a fair number of timeouts
(maybe a dozen) but have not received any communication. I am pretty
sure I'd have no idea they occurred had I not personally witnessed the
error page. I find this a borderline ship blocker for a migration
to Heroku as I consider
I'm following this example, http://github.com/brodyberg/heroku_redis_example
in order to get Resque/Redis working and it seems pretty
straightforward. But when I try and call my super simple Resque class
I get this error / stack trace:
Errno::EAFNOSUPPORT (Address family not supported by
