The latter, once you setup a dyno you're getting build hourly for it.
On Sat, 2010-01-16 at 10:29 -0800, holden wrote:
I have a newb question, but I'm a bit confused on the pricing since it
states on the pricing page estimated monthly cost. I'm not sure how
to phrase my question except as an
Yes, dynos are billed hourly, but I think he was asking whether he
gets billed if the dynos sit there unused. The answer is yes - if you
set the dynos to 8, you'll be paying 35 cents an hour regardless of
how much traffic they're actually processing.
On Jan 16, 12:24 pm, Terence Lee
Hi,
I am using OpenID in my Heroku app HWFeed (http://hwfeed.heroku.com).
Currently, I have the ruby-openid gem setup to put its store in tmp/
openid, but from the Heroku description of the tmp folder, I would
think that this is not the best option. Ruby-openid supports a
memcache option, but the
you can use a database for openid storage.
ruby-openid comes with generators to do this too. I think it's something
like:
./script/generate open_id_authentication_tables MigrationName
./script/generate upgrade_open_id_authentication_tables MigrationName
On Sat, Jan 16, 2010 at 1:30 PM,
So, a cheap man (wise also) could use heroku's API to auto throttle
the dynos each day?
Say, his app is for whatever reason, US centric, or even pacific time
zone only, he could then target a certain set of hours, 8-5 and set
the 8 dynos to the ready at 7:59am, and then then come 5 o'clock mark
Or potentially you could even write your own app to auto-scale a
heroku app yourself based solely on your own usage? ie if the app
maxes out its resources it can simply spawn a new dyno... etc.
Or am I missing something?
On Jan 16, 11:11 pm, holden holden.tho...@gmail.com wrote:
So, a cheap
Nope, you're missing nothing. You can 100% do that, and we have customers
doing that already. For fun recursion, you can include the heroku gem in
your app, and just call heroku dynos X from you app itself. :)
Oren
On Sat, Jan 16, 2010 at 2:15 PM, holden holden.tho...@gmail.com wrote:
Or
Now you've got the complex qusetion. :) What does usage mean. Usually,
you want to scale your dynos when the backlog starts to build up. you can
see the backlog by looking a the HTTP_X_HEROKU_QUEUE_DEPTH header (check
out http://rack-reflector.heroku.com/ to see all the headers). If you're
That's perfect, thank you.
On Jan 17, 12:44 am, Oren Teich o...@heroku.com wrote:
Now you've got the complex qusetion. :) What does usage mean. Usually,
you want to scale your dynos when the backlog starts to build up. you can
see the backlog by looking a the HTTP_X_HEROKU_QUEUE_DEPTH