Re: Minimalistic resque-scheduler for Heroku
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 :https://github.com/clmntlxndr/heroku-scheduler It's an minimalistic app that aim to schedule another one's tasks, using resque-scheduler. It needs one full-time worker from his side ; and one or many workers doing the jobs at the other side, in the main app. What do you think of it ? Do you think about a better solution ? Thanks, Clément -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: paperclip, s3, and configuration
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 and heroku following heroku's
example here:http://docs.heroku.com/s3
ie:
has_attached_file :paper,
:storage = :s3,
:s3_credentials = #{RAILS_ROOT}/config/amazon_s3.yml,
:path = papers/:id/:filename
I have recently started using github as my main git repository to
collaborate with some friends. Because I added github as a remote, I
removed config/amazon_s3.yml from my git repository.
Is there an easy way to configure amazon_s3 for my project without
adding in my configuration file?
Perhaps one way is to do a production branch for heroku, and manage
two remotes? I'm still learning git and this might be a good use to
learn some of the advance features.
Thanks,
Todd
--
You received this message because you are subscribed to the Google Groups
Heroku group.
To post to this group, send email to her...@googlegroups.com.
To unsubscribe from this group, send email to
heroku+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/heroku?hl=en.
Re: Image upload - manipulation - copy to S3
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 am, Oren Teich o...@heroku.com wrote: 1) With Heroku I understand your request can have some temporary space for file uploads. Can I rely on that space to exist for a few minutes while a Delayed Job gets to it? The space is for the request. A delayed job will run as a seperate process, so no, you can't count on it being there. Chances are high that the delayed job will run on a different machine, and not have access to the file. Note that for small files, you can have the dyno upload to s3 as part of the process. Paperclip supports this out of the box. I have sites myself working this way. 2) Does uploading a file completely lock a dyno? Or can a single dyno handle a few simultaneous uploads? A dyno is by definition one simultaneous request. That dyno is locked for the duration of the upload. Oren -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Using resque-scheduler
We're trying to use resque-scheduler with Heroku, but resque-scheduler requires two processes to be running, corresponding to the tasks resque:scheduler (which schedules jobs), and resque:work (which pops jobs off the queue and performs the work). Given that workers on Heroku only run 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...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Custom maintenance page
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 page. I watched the video and followed along ... about as simple as it could be (what else would we expect from Heroku!) ... Oren said that public/ maintenance/index.html would appear, but t did not for me. I manually created public/maintenance/index.html in my Rails root, pushed it up to Heroku, enabled maintenance:on but I still see the default page. What am I missing? Thanks, Bryan -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Custom Error Pages
+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 feature. On Jul 27, 6:20 am, daniel hoey danielho...@gmail.com wrote: Is there anyway to use our own error pages instead of the Heroku ones? -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Rails3 RC from master failed to start
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 w.wnetr...@gmail.com wrote: After pushing application to heroku I get error:http://gist.github.com/510350 Anybody having similar problem? -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
