Re: background jobs are becoming unresponsive regularly
not much to go wrong there really. I'll just add a little teriyaki sauce, and I'm sure my words will be delicious. . -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@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: Is it possible to use CarrierWave on Heroku without relying on cache?
There is an s3 gem upload gem which allows straight from the browser to s3 uploads... gem 's3_swf_upload', :git = 'git://github.com/nathancolgate/s3-swf-upload-plugin' It uses a swf to do it though! -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@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.
How many dynos do I need?
Common question that comes up over and over again. We thought we'll take a crack at this one. Blog: http://labs.mudynamics.com/2011/05/25/blitzio-how-many-dynos-do-i-need-on-heroku/ Code: https://github.com/pcapr/dyno-blitzer Enjoy, K. --- http://blitz.io http://twitter.com/pcapr http://labs.mudynamics.com -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@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: background jobs are becoming unresponsive regularly
well...I meant to add more to my response. Regardless of the problem Heroku resolved, the workers crash an awful lot. I have three of them running I hardly see run for more than 30 minutes. No useful information in the logs, and they crash with or without work to do...meaning the queue can be empty and they fall over. As far as I know, this is a pretty new problem and I wonder if there is an incompatibility in the mix. Maybe a gem that's causing a problem. It's a bit tricky to pin down. On Wed, May 25, 2011 at 8:21 AM, nevinera nevin...@gmail.com wrote: not much to go wrong there really. I'll just add a little teriyaki sauce, and I'm sure my words will be delicious. . -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@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. -- = Brandon Casci Loudcaster http://loudcaster.com = -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@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: background jobs are becoming unresponsive regularly
Hmmm. Could it be that you're running out of memory and crashing without writing to the logs? -p On Wed, May 25, 2011 at 3:10 PM, Brandon Casci bran...@loudcaster.com wrote: well...I meant to add more to my response. Regardless of the problem Heroku resolved, the workers crash an awful lot. I have three of them running I hardly see run for more than 30 minutes. No useful information in the logs, and they crash with or without work to do...meaning the queue can be empty and they fall over. As far as I know, this is a pretty new problem and I wonder if there is an incompatibility in the mix. Maybe a gem that's causing a problem. It's a bit tricky to pin down. On Wed, May 25, 2011 at 8:21 AM, nevinera nevin...@gmail.com wrote: not much to go wrong there really. I'll just add a little teriyaki sauce, and I'm sure my words will be delicious. . -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@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. -- = Brandon Casci Loudcaster http://loudcaster.com = -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@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. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@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: background jobs are becoming unresponsive regularly
Ya, that sounds possible. On Wed, May 25, 2011 at 6:36 PM, Peter van Hardenberg p...@heroku.comwrote: Hmmm. Could it be that you're running out of memory and crashing without writing to the logs? -p On Wed, May 25, 2011 at 3:10 PM, Brandon Casci bran...@loudcaster.com wrote: well...I meant to add more to my response. Regardless of the problem Heroku resolved, the workers crash an awful lot. I have three of them running I hardly see run for more than 30 minutes. No useful information in the logs, and they crash with or without work to do...meaning the queue can be empty and they fall over. As far as I know, this is a pretty new problem and I wonder if there is an incompatibility in the mix. Maybe a gem that's causing a problem. It's a bit tricky to pin down. On Wed, May 25, 2011 at 8:21 AM, nevinera nevin...@gmail.com wrote: not much to go wrong there really. I'll just add a little teriyaki sauce, and I'm sure my words will be delicious. . -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@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. -- = Brandon Casci Loudcaster http://loudcaster.com = -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@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. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@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. -- = Brandon Casci Loudcaster http://loudcaster.com = -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@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: How to handle blog while using Heroku?
Thanks for your reply Alex. I actually didn't know about the cache hits being free, so thanks for letting me know about that. The thing is, I'd like to be able to use a blogging engine, such as Wordpress. I guess the other simple Ruby blogs may work fine, but I'm thinking that there may be some specific Wordpress plugins that I'd want to use. Anyone have any feedback on using a Ruby blog on Heroku, or using Wordpress on another host? Thanks again, Mike On May 24, 6:52 am, Alex a...@heaton.me wrote: If you if you set your cache headers properly, for something like a blog, you can easily scale up to a huge number of visitors. Cache hits are free and fast with Heroku's Varnish layer. Alex On May 23, 11:15 pm, Mike P. michael...@gmail.com wrote: Hi all, I was wondering how you all are handling your blogs while using Heroku as a host? Do you use something like RadiantCMS, or do you host your blog on a separate subdomain elsewhere (e.g.http://blog.mysite.com). I noticed a while back that Shopify had their main site hosted elsewhere, and then whenever someone clicked on their Plans and Pricing page, it would redirect them to their Heroku server (specifically, to a page likehttps://app.shopify.com/signup). I think this is a pretty nice solution, and would avoid me having to pay for scaling on blog visitors. On the other hand, it would be nice to be able to automatically scale with a burst of blog/website visitors. Any ideas on this? How does the single dyno hold up for website and blog visitors? Any advice on this would be greatly appreciated. Thank you, Mike -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@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.
