We actually just ended up running Clockwork on a Tiny EC2 instance to
queue up scheduled jobs. Much less overhead than resque-scheduler,
and very clean. It's about 4 lines of code :)
On Nov 24, 9:10 am, Clément clmntlx...@gmail.com wrote:
Hi all !
You may find this useful
Usually with configuration variables that you don't want to store in
git, you just add environment variables.
On Heroku: heroku config:add S3_KEY=SOMETHING
S3_SECRET=SOMETHINGSECRET
In your app: ENV['S3_KEY']
On Sep 29, 12:19 pm, Todd profes...@gmail.com wrote:
I originally integrated paperclip
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
the jobs:work task, how can we get jobs:work to run
BOTH of these resque jobs? Should we fork inside of the jobs:work
task? Do heroku workers even support fork?
Thanks,
Idris
--
You received this message because you are subscribed to the Google Groups
Heroku group.
To post to this group, send email to her
I've noticed that sometimes the maintenance page is delayed. Try
turning maintenance on and waiting for about 5-10 minutes.
On Aug 24, 11:25 pm, Bryan bryan.a@gmail.com wrote:
I'm trying out 'heroku maintenance:on' for the first time and can't
figure out how to create a custom maintenance
+1 for this feature. If we could just upload static HTML pages for
the different possible heroku errors, that would be great. It's
unacceptable for a Heroku branded error to come up no matter what the
error is.
On Aug 6, 6:41 am, Tomaž Žlender tomaz.zlen...@gmail.com wrote:
+1 for this
Yes I'm also having this problem, with our own gem on github. Anyone
have a solution to this?
On Aug 5, 5:11 pm, lstoll l...@lds.li wrote:
I'm having a similar problem - seems that any gem that is installed
from a git source will fail like this.
On Aug 5, 10:47 pm, morgoth
