81–90 of 151 posts
Earlier quoted context omitted.
Any suggestions on a rival PaaS that has a similar engineering philosophy to the old Heroku?
If you want a more minimal do-it-yourself option you could self-host something like Dokku[1]. [1] https://dokku.com/
Earlier quoted context omitted.
I assume it’s so that they can mine your LinkenIn connection data and make it available to their sales teams to upsell you and people you know. I’d imagine they would end up storing all that data in some kind of web-based CRM, possibly sold as a SAAS product.
Hmm, yeah, maybe one where with "sales" in its name. I think you're into something here.
> 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…
It is difficult for me to understand why Salesforce is not aware of the strength of the Heroku brand among experienced technology workers, and how much they have destroyed that brand in the last 2-3 years.
If you're on Heroku how do you deploy now? It says it's still weeks away before you can deploy - did I read this right?
Still weeks away from enabling the GitHub integration again, you can still manually deploy via the heroku CLI. Our team realised heroku was going to take weeks and we’ve replicated our “review app” development workflow with GitHub actions that clone apps on PR, push code and rebuild them on push and destroy them on PR close. It’s not as seamless as the heroku GitHub integration but it’s good enough for now.
> 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…
Guess I'm packing it up as I'm no longer seen as target audience (its my hobby project platform)
> New features have been banned for years. Only "keep the lights on" projects are allowed.
What???
Earlier quoted context omitted.
Sorry but Render at their lunch entirely. Try it. https://render.com/docs/deploy-rails Want simple? Use a build.sh Want a bit complexity? Use a Dockerfile. Their docs are really copy paste for 99.9% applications. Whoever in that company made the decision to invest in docs was right on the money. It made switching to them a much easier choice. https://render.com
> Whoever in that company made the decision to invest in docs was right on the money. Also the reason Django has always been so approachable (particularly in the early days, as it is orders of magnitude more complex now) and therefore popular Older still, IMHO also why mIRC scripting was so much fun despite its shortcomings. The help file had literally everything you could want to learn about the language and it almo…
> 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…
> Additionally, we have no evidence that the attacker has accessed any customer accounts or decrypted customers’ environment variables. Now the attackers had access to encrypted environment variables?
More context, from the latest email notification: > We also wanted to address a question regarding impact to environment variables. While we confirmed that the threat actor had access to encrypted Heroku customer secrets stored in config var, the secrets are encrypted at rest and the threat actor did not access the encryption key necessary to decrypt config var secrets.
If the threat actor had access to any of the systems that use the key, they may not have needed to. Even this statement isn't clear that they couldn't have done it, but suggests that they don't think it's true...
This is really bad incident response messaging.
> 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…