And I just finished migrating my portfolio database from MongoDB Atlas to Heroku pg
Removal of Heroku free product plans
121–130 of 590 posts
Re: Removal of Heroku free product plans
#122Earlier quoted context omitted.
It doesn't require a login when accessed using a private browsing window or a browser profile that hasn't been logged into Heroku before.
I wonder what purpose this particular dark pattern serves? Edit: Perhaps accounts that authenticate on this page, and that are also taking advantage of free tiers, are being segmented for upsell. It is at least an indicator they are interested enough to read this news.
I’ve noticed the AWS Forums does this too. In practice it just means I avoid using it.
Re: Removal of Heroku free product plans
#123that's a damn shame, just as I was starting to investigate using it more frequently as well...
Re: Removal of Heroku free product plans
#124And today is the day I will no longer use heroku. There's goes their free tier.
Re: Removal of Heroku free product plans
#125all appears like the classic playbook of "Acquisition by a big company who predominantly has an enterprise sales GTM which then kills the self serve channel as they cannot evaluate the value it brings". in a few years said company goes, "why have we lost our acquisition funnel and aren't relevant to the developer community and why is X new service taking share from us?"
Re: Removal of Heroku free product plans
#126> Starting October 26, 2022, we will begin deleting inactive accounts and associated storage for accounts that have been inactive for over a year. Inactive for over a year? That's really interesting, because I was a paid Heroku customer for multiple years, but am no longer. I don't even have resources running, but I do have a few apps sitting in the dashboard. I guess I'm fair game for culling, despite being a paid c…
I don't wish Salesforce the best of luck with anything.
Re: Removal of Heroku free product plans
#127Re: Removal of Heroku free product plans
#128Link to the public roadmap: https://github.com/orgs/heroku/projects/130 Blog post says "Salesforce has never been more focused on Heroku's future." but this looks like they are just keeping the lights on by deprecating and keeping security up to date. Which isn't bad if the product has reached maturity but I wonder if these really are the most important features users ask for. Why does the feedback link on the blog p…
We are doing more than keeping the lights on. Purpose of the public roadmap (which just launched, we'll need some time to really get it right, I'm sure) is to show what we are working on. Any comment on the work around github integration safety as an example? Watching for feedback here, but it's nice to know when I'm getting reachouts on product feedback directly who is touching base. Linked-in is great for that. But…
You are honestly trying to tell me that a developer-focused company has no better way to get user feedback?
Issue tracker? Idea tracker (check this as an example: https://circleci.canny.io/)? Customer support? Email?
Re: Removal of Heroku free product plans
#129Earlier quoted context omitted.
In our case, this would mean increasing our Heroku bill by 400% (we run a few paid apps and >40 free dynos with super low monthly activity) Does anyone have a recommendation how to re-create the Heroku experience on AWS or Azure?
AWS beanstalk allows you to run on very cheap instances, even cheaper if you get a plan and commit to a term. It’s not a 1:1 experience, but I’ve enjoyed it as an alternative to Heroku for sure. Alternatively, you could spin up a server and install dokku which is pretty close to a shipping experience, but still requires some maintenance and hand holding.
I switched from heroku to dokku (and DigitalOcean) last month. Overall: easy to adapt from heroku since so many of the concepts (and commands) are the same.
I tried to get too fancy and set two web services on the same app (since the DO droplet was giving me more CPU and 4x the RAM for half the price) but they seemed to battle each other for control of the database and/or were exceeding resources. So I chilled out and used 1 web service and set CPU and RAM resource limits. And... it's been smooth since then! Much faster than heroku, too.
Price-wise: we were on the $50/mo dyno plus $9/mo postgresql, and with DO we beefed up the managed database specs, and now get 4x the RAM on the droplet, and the total cost is the same as heroku.
We do still have a free tier staging server on heroku that we only use a couple times a year.
Oh shoot, I just remembered that I use staticman for processing comments on a couple jekyll blogs, and those use free heroku tiers. Argh!
Re: Removal of Heroku free product plans
#130So their next chapter is obscurity followed by shutting down? It was clear even before their horribly bungled GitHub security incident that Heroku was on life support at best and it's been a long time since "Heroku" was the answer to "What PaaS should I use?". The beancounters took control a while back and are sucking all they can out of it before they discard it's empty shell. Having Heroku as your PaaS provider see…
What is the PaaS people use today? Just big cloud is too powerful or are there still niche companies that make life easy for startups like Heroku used to?
Railway is super easy to get started. Render and Fly are good options too