Re: free vs. paid heroku app performance
It's in the best interest of any web site operator to know when their web site is down external from your hosting company regardless of platform, language, or baseline hosting provider's functionality. When I get a phone call at 2am that the web site is down, I should already be on it. It just happens that it has the same benefits for spun down processes. I understand where you're coming from in regards to all the free sites but most likely the operators of those sites are leveraging Varnish and site monitoring is simply going to hit the same cached route. We can only work with what we have, if they want it done differently - give us the option. Besides, I pay plenty a month for it to work in my situation. /david. On Aug 27, 10:52 am, Stefan Wintermeyer stefan.winterme...@amooma.de wrote: Am 27.08.2010 um 15:27 schrieb David: That's what we do, setting up site monitoring is part of my normal routine so I have something checking the site every 5 mins including staging. I think that might not be in the best interest of the Heroku guys. If they wanted it that way they'd have built it in. Stefan -- AMOOMA GmbH - Bachstr. 126 - 56566 Neuwied -- http://www.amooma.de Geschäftsführer: Stefan Wintermeyer, Handelsregister Montabaur B14998 Asterisk 1.6:http://das-asterisk-buch.de Ruby on Rails 3:http://ruby-auf-schienen.de Videos and slides of AMOOCON:http://amoocon.de -- 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: where is the support?
fyi. I was having a similar problem. - Heroku receiving push - Rails app detected - Configuring New Relic plugin... done. Installing the New Relic plugin... done. Compiled slug size is 10.8MB - Launching... failed (Heroku error) ! Previous app version is still running, try pushing again shortly ! We've been notified, see http://support.heroku.com if the problem persists ! Heroku push rejected, app timed out during publish error: hooks/pre-receive exited with error code 1 making a change to a config file seemed to clear up the issue. On Aug 25, 5:20 pm, Jesse jesse.ho...@gmail.com wrote: David, I finally got a chance to reply on the support ticket; was away from computer until now tried both suggested options but not working Thank you for reply On Aug 25, 1:11 pm, David Dollar da...@heroku.com wrote: Your slug compile might have gotten stuck. Try pushing another trivial commit or changing a config var to trigger another compile. Cheers, David On Aug 25, 2010, at 3:57 PM, Jesse wrote: I have executed heroku restart heroku maintenace:off multiple times both run without failure I can even heroku console and execute commands at that level, it is just that all web requests hit the maintenance page nothing is written to the logs, seems like maybe some type of caching issue on the Heroku web servers? doesn't seem like anything that can be solved without intervention from heroku? On Aug 25, 12:48 pm, Daniel Spangenberg daniel.spangenb...@googlemail.com wrote: Have you tried to restart your app or push again oder change an config variable? Daniel Am 25.08.2010 um 21:41 schrieb Jesse: My site is stuck in maintenance mode I submitted a ticket to Heroku 18 hours ago - it is still unassigned I don't see any issues listed athttp://status.heroku.com/ Heroku support where are you? - Jesse -- 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 athttp://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 her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group athttp://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 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: free vs. paid heroku app performance
I think I have to agree with Stefan - *particularly* when it comes to staging. Why not take the cheapest entry level package for staging for a month - any outfit that advertises rock solid ruby platform should give good to excellent service for even the cheapest paid-for package. I totally agree with your previous post and its sentiments - the need to be aware of, and working on, the problem when the client calls at 2:00 a.m. is critical - it has to be one of the worst feelings ever to have your client inform you the site is down and not be aware of it. However the discussion started on the topic the free account's (staging) performance ... doesn't surprise me it's poor to fair ... On Aug 28, 1:43 pm, David datab...@gmail.com wrote: It's in the best interest of any web site operator to know when their web site is down external from your hosting company regardless of platform, language, or baseline hosting provider's functionality. When I get a phone call at 2am that the web site is down, I should already be on it. It just happens that it has the same benefits for spun down processes. I understand where you're coming from in regards to all the free sites but most likely the operators of those sites are leveraging Varnish and site monitoring is simply going to hit the same cached route. We can only work with what we have, if they want it done differently - give us the option. Besides, I pay plenty a month for it to work in my situation. /david. On Aug 27, 10:52 am, Stefan Wintermeyer stefan.winterme...@amooma.de wrote: Am 27.08.2010 um 15:27 schrieb David: That's what we do, setting up site monitoring is part of my normal routine so I have something checking the site every 5 mins including staging. I think that might not be in the best interest of the Heroku guys. If they wanted it that way they'd have built it in. Stefan -- AMOOMA GmbH - Bachstr. 126 - 56566 Neuwied -- http://www.amooma.de Geschäftsführer: Stefan Wintermeyer, Handelsregister Montabaur B14998 Asterisk 1.6:http://das-asterisk-buch.de Ruby on Rails 3:http://ruby-auf-schienen.de Videos and slides of AMOOCON:http://amoocon.de -- 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.
heroku create command appears to hang
Been waiting a long time now for my heroku create command to finish. I can see the app when I log in to my account on heroku.com, but I do not expect to be able to work on the app until the command finishes. Anything I should check? Thanks. -- 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.
