7 ms·

This does actually work, however be warned this will incur costs on your heroku account. EDIT: False alarm, Heroku billing has changed so the application did n

This does actually work, however be warned this will incur costs on your heroku account. EDIT: False alarm, Heroku billing has changed so the application did not fall into my free dyno range.

teich 15y ago
You get the same 750 hours free usage as all other apps.
- chewbranca 15y ago
  Following the steps in that gist, I have a heroku clojure app up that just created an invoice line item for 1 worker. It was only for a few minutes, but I definitely just got charged for it.
  - deleted 15y ago
    [deleted]
  - milkshakes 15y ago
    http://devcenter.heroku.com/articles/billing-changes http://devcenter.heroku.com/articles/billing-changes On June 1, 2011, Heroku switched from billing for “dynos” to billing for “dyno-hours”, which is more clear. This brings pricing inline with the new process model, wherein you can run one-off processes as well as manipulate the dynos for each of your app’s process types independently. The vast majority of apps will see a 1% - 10% reduction in overall monthly dyno charges. Previously, Heroku included “1 free dyno” with each app, which is equivalent to between 672 and 744 dyno-hours (depending on the length of the month). With this switch to dyno-hours, we are converting the included free dyno to a fixed 750 free dyno-hours. This makes more sense, is more consistent, gives all users additional free dyno-hours, and allows the free dyno-hours to be used for any kind of process (web, workers, one-off admin process, or any other Procfile process).
    - chewbranca 15y ago
      Ahhhh that would be why, I didn't notice the 'future' billing change that is supposed to happen tomorrow. I'll edit my original post to clarify. On a more serious note, thanks for the great work Heroku! Very excited to see you guys turning into a generic service platform with a strong API based addon presence.
  - deleted 15y ago
    [deleted]
burke 15y ago
To the tune of probably 1 or 2 cents. Not saying it shouldn't be mentioned, but let's not scare people away here.

This does actually work, however be warned this will incur costs on your heroku account. EDIT: False alarm, Heroku billing has changed so the application did not fall into my free dyno range.

teich 15y ago

You get the same 750 hours free usage as all other apps.

chewbranca 15y ago
Following the steps in that gist, I have a heroku clojure app up that just created an invoice line item for 1 worker. It was only for a few minutes, but I definitely just got charged for it.
- deleted 15y ago
  [deleted]
- milkshakes 15y ago
  http://devcenter.heroku.com/articles/billing-changes http://devcenter.heroku.com/articles/billing-changes On June 1, 2011, Heroku switched from billing for “dynos” to billing for “dyno-hours”, which is more clear. This brings pricing inline with the new process model, wherein you can run one-off processes as well as manipulate the dynos for each of your app’s process types independently. The vast majority of apps will see a 1% - 10% reduction in overall monthly dyno charges. Previously, Heroku included “1 free dyno” with each app, which is equivalent to between 672 and 744 dyno-hours (depending on the length of the month). With this switch to dyno-hours, we are converting the included free dyno to a fixed 750 free dyno-hours. This makes more sense, is more consistent, gives all users additional free dyno-hours, and allows the free dyno-hours to be used for any kind of process (web, workers, one-off admin process, or any other Procfile process).
  - chewbranca 15y ago
    Ahhhh that would be why, I didn't notice the 'future' billing change that is supposed to happen tomorrow. I'll edit my original post to clarify. On a more serious note, thanks for the great work Heroku! Very excited to see you guys turning into a generic service platform with a strong API based addon presence.
- deleted 15y ago
  [deleted]

burke 15y ago

To the tune of probably 1 or 2 cents. Not saying it shouldn't be mentioned, but let's not scare people away here.