hi guys: just installed the delayed_jobs gem and am now getting this
error.
rake aborted!
Don't know how to build task 'jobs:work'
Has anyone had this error?
Thanks...Chris
--
You received this message because you are subscribed to the Google Groups
Heroku group.
To post to this group, send
Ahhh good old rake errors!
See if you can get a worker to start up with --trace. See if you can kick of
DelayedJob locally too..with --trace. you may get the same exception.
You might find that something is preventing all the necessary tasks from
loading.
I was migrating over to Heroku. I had a
I can't upload my database:
heroku db:push
Auto-detected local database: sqlite://db/development.sqlite3
! Internal server error
An idea?
Best regards, Olivier
--
You received this message because you are subscribed to the Google Groups
Heroku group.
To
Did it used to work or is this your first try? How do the schemas compare?
On 28 September 2010 11:04, Olivier R orouch...@gmail.com wrote:
I can't upload my database:
heroku db:push
Auto-detected local database: sqlite://db/development.sqlite3
! Internal server error
I didn't even have the chance push it on the first try. It's the first
time it happens amongst all my applications.
Are there any other way to mirror both dbs?
On Sep 28, 12:13 pm, Hemal Kuntawala hemal.kuntaw...@gmail.com
wrote:
Did it used to work or is this your first try? How do the schemas
I re-installed heroku and taps gems on my machine and it solved the
issue.
On Sep 28, 1:02 pm, Olivier R orouch...@gmail.com wrote:
I didn't even have the chance push it on the first try. It's the first
time it happens amongst all my applications.
Are there any other way to mirror both dbs?
Why not just upload the file straight to S3 (I recommend not going
through paperclip, but instead going straight to S3, so you don't hold
up the dyno). Then when the upload finishes, kick off a background
job to read the image off S3, process it, and save the processed
image.
On Sep 28, 12:07
After turning on debug mode in production I see the following error
when loading the request:
Unexpected exception performing discovery for id EXAMPLE.com: Error
connecting to SSL URL
https://www.google.com/accounts/o8/.well-known/host-meta?hd=EXAMPLE.com:
SSL_connect returned=1 errno=0
On Sep 28, 11:12 am, Idris idr...@gmail.com wrote:
Why not just upload the file straight to S3 (I recommend not going
through paperclip, but instead going straight to S3, so you don't hold
up the dyno). Then when the upload finishes, kick off a background
job to read the image off S3, process
