Live data from Hacker News

Heroku: We’ve Heard Your Feedback

blog.heroku.com

131–140 of 151 posts

Re: Heroku: We’ve Heard Your Feedback

#131

Earlier quoted context omitted.

> 2. Customers sign up at "heroku.com", the platform is called "Heroku", the CLI is "heroku", everything's heroku, so don't send emails from a parent company (Salesforce), send them from "Heroku". They're working on something called "Project Periwinkle" that is intended to remove all Heroku branding and make everything Salesforce branded. Periwinkle being a colour between blue (salesforce) and purple (heroku). No mor…

> New features have been banned for years. Only "keep the lights on" projects are allowed. That's what it's looked like from the outside -- that no features were for whatever reason(s) no longer going to happen. But still dismaying to hear it from the inside in those terms.

You've gotta go way back on the Heroku Changelog to find anything that isn't a language version upgrade or feature removal: https://devcenter.heroku.com/changelog

I think the feature freeze happened in 2018

Re: Heroku: We’ve Heard Your Feedback

#132
post #18

> We’ve heard your feedback on our communications during this incident. You want more transparency, more in-depth information, and fewer “we are working on it” posts. Well, those, and : 1. Speed. It took days for heroku customers to be told about this. 2. Customers sign up at "heroku.com", the platform is called "Heroku", the CLI is "heroku", everything's heroku, so don't send emails from a parent company (Salesforce…

> 2. Customers sign up at "heroku.com", the platform is called "Heroku", the CLI is "heroku", everything's heroku, so don't send emails from a parent company (Salesforce), send them from "Heroku". They're working on something called "Project Periwinkle" that is intended to remove all Heroku branding and make everything Salesforce branded. Periwinkle being a colour between blue (salesforce) and purple (heroku). No mor…

Youch.

I have paid apps and free apps (staticman comment processing, and very simple apps I create while following learning tutorials). This project sounds bad! I’ve been slowly exploring alternatives, and was about to abandon my search due to demands on my time. Guess I need to keep exploring.

Re: Heroku: We’ve Heard Your Feedback

#133

Earlier quoted context omitted.

I was a long time Heroku user/lover (~10 years) for both personal and company projects. I've recently moved to Render[1], and so far it's been great. I haven't been using them long enough to put it through it's paces, but I'd certainly say it's worth a look. Other alternatives I've heard good things about are Fly.io[2] and Porter[3]. [1] - https://render.com/ [2] - https://fly.io/ [3] - https://porter.run/

Checked out render.com in the context of side projects that I want on the air but don't expect anyone to ever use (I have so many on heroku, who got rewarded for their generosity with many thousands of dollars of business from me), which means I'm willing to pay a few dollars but not to pay per-app. Looks great except that they delete your free databases after 90 days, making it completely useless for this use case.…

What about DO App Platform? I was thinking of trying that next. I’ve read a lot about slow build times and random build failures, but at the same time they at least seem to be actively developing the service.

Re: Heroku: We’ve Heard Your Feedback

#134

Earlier quoted context omitted.

I'm moving a small amount of stuff ($250/mo spend) off Heroku this weekend. It's either Render or Fly, and I guess I'm going to start with Render. Here's where I'm starting: https://render.com/docs/migrate-from-heroku

Update: Migrating the simplest possible Rails app from free-tier to free-tier didn't work on Render (deploys fail, no logs to be found), so I'm bailing out to try Fly. To any render people reading this, it appears to have been an issue with the migration plugin and the Heroku-18 stack. Manually deploying the app worked fine.

Thanks for the heads up and good to hear you were able to deploy the app manually. We might deprecate the migrator because it's hard to keep up with all the Heroku stack and buildpack configs and because manual migrations are relatively straightforward.

Re: Heroku: We’ve Heard Your Feedback

#135
post #134

Earlier quoted context omitted.

Update: Migrating the simplest possible Rails app from free-tier to free-tier didn't work on Render (deploys fail, no logs to be found), so I'm bailing out to try Fly. To any render people reading this, it appears to have been an issue with the migration plugin and the Heroku-18 stack. Manually deploying the app worked fine.

Thanks for the heads up and good to hear you were able to deploy the app manually. We might deprecate the migrator because it's hard to keep up with all the Heroku stack and buildpack configs and because manual migrations are relatively straightforward.

Completely understandable. I’ve been configuring stuff with Render all morning and I’m really starting to like this service.

Is there a way to assign an existing Env Group when manually creating a new service? So far I've needed to create and then go back in and assign.

Re: Heroku: We’ve Heard Your Feedback

#136

Earlier quoted context omitted.

> New features have been banned for years. Only "keep the lights on" projects are allowed. That's what it's looked like from the outside -- that no features were for whatever reason(s) no longer going to happen. But still dismaying to hear it from the inside in those terms.

You've gotta go way back on the Heroku Changelog to find anything that isn't a language version upgrade or feature removal: https://devcenter.heroku.com/changelog I think the feature freeze happened in 2018

The interesting thing is that heroku still is so at the top of what it does, as far as developer UX and ease and reliability. It's hard to describe exactly what i mean, but I know plenty of other people agree. Other things do other things better -- but it's only in the past year or two that some things have started to come close or equal.

I don't know what's going on exactly. Those who set up heroku for the first ~5 years somehow did such a good job that they could coast for another 5-10 and still stay on top of what they were on top of.

Re: Heroku: We’ve Heard Your Feedback

#137
post #134

Earlier quoted context omitted.

Thanks for the heads up and good to hear you were able to deploy the app manually. We might deprecate the migrator because it's hard to keep up with all the Heroku stack and buildpack configs and because manual migrations are relatively straightforward.

Completely understandable. I’ve been configuring stuff with Render all morning and I’m really starting to like this service. Is there a way to assign an existing Env Group when manually creating a new service? So far I've needed to create and then go back in and assign.

Thanks! Re: Env Groups, not yet, but we are overhauling the new service flow and will definitely incorporate adding env groups.

Re: Heroku: We’ve Heard Your Feedback

#139
post #98
post #12

Earlier quoted context omitted.

You have to make sure the attackers aren’t still in your network, you have to get them out if they are, you have to fully scope out what they messed with, and restore anything that’s plausibly connected. Even in the best case with all the right monitoring systems in place there is a lot of manual work involved from owners of the various different effected services and just managing the overall response adequately. I…

Wouldn’t you hire an incident response team who are experts in figuring this stuff out?

Depends. Often yes but at Heroku/Salesforce’s scale you really need a lot of security expertise in-house too.

Re: Heroku: We’ve Heard Your Feedback

#140

Earlier quoted context omitted.

Checked out render.com in the context of side projects that I want on the air but don't expect anyone to ever use (I have so many on heroku, who got rewarded for their generosity with many thousands of dollars of business from me), which means I'm willing to pay a few dollars but not to pay per-app. Looks great except that they delete your free databases after 90 days, making it completely useless for this use case.…

What about DO App Platform? I was thinking of trying that next. I’ve read a lot about slow build times and random build failures, but at the same time they at least seem to be actively developing the service.

Elsewhere in this thread is a link to a blogpost comparing it to doing things manually with GCP and quickly dismissing it as extremely limited, so I didn't delve further.
Post reply on HN