Re: Database timeouts
Some follow-up to my own post in case someone else has the same issue. I looked into putting the schema scans into the to_prepare callback but it looks like that is run at start-up (for production). Also on further reflection moving the schema scans out of the startup (or altogether) only reduces the issue a bit. The fundamental issue of database timeouts still causes errors during the request cycle. If this continues I will just have to conclude Heroku is not a reliable hosting environment if you are not able to justify the $200+/month for a dedicated database (using Amazon RDS might be a little cheaper but still expensive for an app that doesn't need a dedicated database). I am *hoping* this is just a temp issue with Heroku that will get resolved soon. So in the meantime I created a restart app for my client so they can restart the application themselves if it gets a database hangup. It feels like I am back developing on Windows with having a restart script but it will have to do for now. In case someone else might need something similar here is the code for the restart app: http://gist.github.com/371030 Hopefully reliability won't force me to move from Heroku as I really love the workflow they provide. -- 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: What logs get stored by heroku?
we store only ncsa style logs. We don't even store your output from heroku logs - hence only 100 lines. Oren On Mon, Apr 19, 2010 at 1:20 AM, Alex a...@heaton.me wrote: I've got a little sinatra password generating application that I'm confident is secure, but I wanted to make sure no compromising info is being stored in heroku (also, I'm curious). Obviously there are the main logs that sinatra or rails or other frameworks set up, but is there *anything* else that heroku stores behind the scenes about my requests and processes? Looking at my 'heroku logs' output, I'm good, but I wanted to make 100% sure that there isn't anything else being stored anywhere. Thanks, Alex -- 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.comheroku%2bunsubscr...@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 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.
Default index page on Heroku server
Hi all,
I'm having a problem with the default index page on an app I've
recently uploaded to http://lebronandkobe2.heroku.com.
I want my custom signatures controller to appear instead of the the
standard Rails welcome screen. I changed config/routes.rb
(map.root :controller = signatures), which works on my local
Mongrel server. However it does not work on Heroku. I also ran
heroku rake routes which reports that my change should have worked.
From the log file:
root/
{:action=index, :controller=signatures}
Any advice is much appreciated!
(FYI, the page I am trying to load by default is available
http://lebronandkobe2.heroku.com/signatures)
Thanks!
Brett
--
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: Default index page on Heroku server
Did you remove public/index.html?
Oren
On Mon, Apr 19, 2010 at 4:15 PM, Brett brett.huneyc...@gmail.com wrote:
Hi all,
I'm having a problem with the default index page on an app I've
recently uploaded to http://lebronandkobe2.heroku.com.
I want my custom signatures controller to appear instead of the the
standard Rails welcome screen. I changed config/routes.rb
(map.root :controller = signatures), which works on my local
Mongrel server. However it does not work on Heroku. I also ran
heroku rake routes which reports that my change should have worked.
From the log file:
root/
{:action=index, :controller=signatures}
Any advice is much appreciated!
(FYI, the page I am trying to load by default is available
http://lebronandkobe2.heroku.com/signatures)
Thanks!
Brett
--
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.comheroku%2bunsubscr...@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 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: NOTICE: Memcached exiting beta
Sounds good. I wasn't a member of the beta - was the flush_all function ever added? I don't see it in the docs. Thanks On Apr 19, 5:48 pm, Oren Teich o...@heroku.com wrote: Hi all, We're excited to announce that we'll be taking memcached out of beta this week. We will have a few plans to meet different needs: 5MB - Free 100MB - $20/month 250MB - $40/month 1GB - $90/month 10GB - $800/month 50GB - $3500/month All existing users of the memcached add-on will be grandfathered for 2 weeks. After two weeks, you will be charged at the 100MB plan level ($20/month). Please let me know if you have any questions. 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 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.
