Re: Basic Production Site

2010-03-08 Thread Oren Teich
Correct, daily. Oren On Mon, Mar 8, 2010 at 1:41 PM, DAZ wrote: > Sorry just one more question in reply to Oren - how often do you > backup for disaster recovery purposes, daily? > > cheers, > > DAZ > > > > On Mar 8, 9:06 pm, Oren Teich wrote: > > Everything is fully backed for disaster recover

Re: Basic Production Site

2010-03-08 Thread DAZ
Sorry just one more question in reply to Oren - how often do you backup for disaster recovery purposes, daily? cheers, DAZ On Mar 8, 9:06 pm, Oren Teich wrote: > Everything is fully backed for disaster recovery purposes.  We don't provide > user accessible backups - it's only in case somethin

Re: Basic Production Site

2010-03-08 Thread DAZ
Thanks to all of you taking the time to make this much clearer. Looking forward to getting it all set up. Thanks again, DAZ On Mar 8, 9:20 pm, Carl Fyffe wrote: > There is an add-on for New Relic:http://addons.heroku.com/newrelic > > Basically you want to watch how long your response time is

Re: Basic Production Site

2010-03-08 Thread Carl Fyffe
There is an add-on for New Relic: http://addons.heroku.com/newrelic Basically you want to watch how long your response time is using the Apdex Scoring to determine if your site is fast enough for the traffic that you have. http://newrelic.com/features.html#ApdexScoring With the traffic that you h

Re: Basic Production Site

2010-03-08 Thread Terence Lee
You would add dynos to increase the number of rails instances that are run concurrently, so you can scale your site. Workers would correspond to background jobs. -Terence On Mon, 2010-03-08 at 13:10 -0800, DAZ wrote: > Thanks Oren, > > That's useful as a starting point. What do I use to 'see ho

Re: Basic Production Site

2010-03-08 Thread Terence Lee
I've never come near the limit. I think Oren or someone from Heroku reaches out to you. -Terence On Mon, 2010-03-08 at 13:07 -0800, DAZ wrote: > Thanks for that Terence, > > Just a question about your last point. How do I choose which plan? Say > I went for the free plan (Blossom), how do I know

Re: Basic Production Site

2010-03-08 Thread DAZ
Thanks Oren, That's useful as a starting point. What do I use to 'see how it goes' - sorry I'm new to this game and not sure if I'd know if the site was performing well or not. What do you mean when you say 'scaling traffic instantly' - why would I add dynos and/or workers? cheers, DAZ On Mar 8

Re: Basic Production Site

2010-03-08 Thread DAZ
Thanks for that Terence, Just a question about your last point. How do I choose which plan? Say I went for the free plan (Blossom), how do I know if it needs upgrading - does it crash, do I get an email warning or does it just increase as needed and then I get charged? cheers, DAZ On Mar 8, 8

Re: Basic Production Site

2010-03-08 Thread Oren Teich
Everything is fully backed for disaster recovery purposes. We don't provide user accessible backups - it's only in case something goes wrong with the systems. This includes your DB and your app. Start on a koi + 1 dyno, and see how it goes. You can scale the traffic instantly. Oren On Mon, M

Re: Basic Production Site

2010-03-08 Thread Terence Lee
Answers below. On Mon, 2010-03-08 at 12:31 -0800, DAZ wrote: > Hi, > > I'm planning on launching a production site using Heroku, but have a > few questions: > > 1) Are sites that are hosted on Heroku backed up or do I have to do it > manually - what is the procedure for doing this? You have to d

Basic Production Site

2010-03-08 Thread DAZ
Hi, I'm planning on launching a production site using Heroku, but have a few questions: 1) Are sites that are hosted on Heroku backed up or do I have to do it manually - what is the procedure for doing this? 2) Is the database backed up as well? 3) How does the pricing work? This site has around