Closed capeterson closed 2 years ago
Hoping to have a material update here in the next week or two, stay tuned.
At Dreamforce this week presented this update - more news coming soon!
We just posted to the heroku blog with details on the changes: https://blog.heroku.com/new-low-cost-plans. Thanks to everybody who shared feedback however you sent it.
Sometime ago I opened an issue about keeping the free tiers for staging apps in a pipeline which, in general, are not accessed frequently (see #54). I feel that the new low-cost plans announced is a very good step that corrects (some of) the unfairness. Specifically,
In order to not be charged for something that is "just sitting there", I am currently considering of making a backup of the staging app database, detach it when I am not going to use it for a long time and then attach it again and restore the backup when work needs to be done.
How about offering the above functionality as an option to "park and unpark" a database from the Heroku platform or CLI?
@capeterson let me add two points:
1/ As an enterprise customer I do not want to have to update all my review apps to hobby if I have one of them that is incidentally running for too long (it happened to us in the past with some webhooks notification) I would rather have an option on the review apps to limit their running time or an way to add some more hours for fixed pricing (a quick way to unblock the situation)
2/ We sometimes have review apps that are staying open for some time. I know there is the auto-destroy but it would be great if we could have a eco PG that would basically shutdown the database when the dyno is shutting down. (I would rather have it automated than to have to do it from the command line)
3/ Currently we do not have access to the hobby tier as an entreprise customer, will we get access to hobby and eco dynos ?
This is also valid feedback for #49 @afawcett
What about including 1 or couple of free ECO PostgreSQL DB's with the $5 ECO DYNO? I think the $5 ECO Dyno is a pretty awesome idea to have it spread over all of your "ECO" apps and have it sleep. This is really perfect for the DYNO part of the APP Picture.
The DB Part is still a little pricy for people who just occasionally have the need. If you can't include any free DBs with the $5 PAID Eco Dyno then what about offering SQLite for free with the ECO DYNO or offer it for something really cheap like a $1 or $2 per instance. Keep your PostgreSQL for the apps that REALLY need it. Hobby or testing apps probably don't need PostgreSQL. I have a Hobby FoodLogger app that only myself and my GF really use and it would be fine with SQLite. I don't know if there is another reason why you don't allow SQLite (Technical reason IE some kind of incompatibility with the Platform or?).
Hello @capeterson , thank you for leading this important change in Heroku plans! The end of November is closer and closer and so is the end of the Free Tier. When should we expect the Eco plans to be available? It would be great to have 1-2 weeks to migrate. Thanks in advance! Lukasz Czerwinski CTO of EonD
Hello @capeterson , thank you for leading this important change in Heroku plans! The end of November is closer and closer and so is the end of the Free Tier. When should we expect the Eco plans to be available? It would be great to have 1-2 weeks to migrate. Thanks in advance! Lukasz Czerwinski CTO of EonD
Piggybacking on this. Looks like the "mini" addons are available to Postgres and Redis. However, specifying something like heroku-postgresql:mini
or heroku-redis:mini
for the plan in app.json for review apps is still provisioning a Hobby instance. Would be nice if that would start provisioning mini instances as well so we can start moving ahead of time.
These plans are live! With a graphical migration tool available in the Heroku Dashboard as well. Take a look at https://blog.heroku.com/eco-and-mini-plans-ga
@irphilli let me take a look at this and get back to you.
@irphilli there's a few behind the scenes issues with how the pipelines consent process is interacting here, sadly I don't think we'll be able to fix this before the Nov 28th end of hobby plans. We have a test case for this now though, so thank you for flagging, and apologies we can't make the migration easier in the interim.
@capeterson from https://devcenter.heroku.com/articles/ruby-database-provisioning
By default, the lowest-cost Heroku Postgres plan will be added to any Ruby app that has the
pg
gem dependency, when deployed for the first time.
How will this behave after Nov 28th? Can I disable it? (I really don't need it.)
@dentarg sorry about the slow response. Yes, you can make Heroku skip auto-provisioning the database by setting the HEROKU_SKIP_DATABASE_PROVISION=1
config var. Details on Dev Center.
@friism Thanks for following up! I'm aware and using that, I created the ticket @schneems resolved with https://github.com/heroku/heroku-buildpack-ruby/pull/1349 :-)
We've heard quite a bit of feedback about the need for low-cost options for active development use, lightweight review apps, and other similar use cases that don't require a fully "production" level app but want dev/prod parity. We're taking a look at what we can do to make this kind of lightweight use case that was previously well serviced by the free tier into something we carry forward as a lower cost than other options.