That, err, took a while. I mean I'm excited and I can't imagine the complexities of adding it to something as massive as Heroku, but Salesforce have a lot of money to chuck at stuff if they wanted and stuff like HTTP/2 shouldn't be an announcement in 2024!
How do I tell Heroku to not install install the #nodejs buildpack at all?
(and remediate this WARNING on every deploy)
WARNING:
Installing a default version (20.9.0) of Node.js.
This version is not pinned and can change over time, causing unexpected failures.
Heroku recommends placing the heroku/nodejs buildpack in front of heroku/ruby to install a specific version of node
Whenever I see a #Kubernetes post that starts with “it’s too complicated or it doesn’t solve any problems”, I can’t help but roll my eyes a bit.
Do you need to use it? No, but if you do adopt it, it allows for effectively unlimited growth with none of the maintenance that drags down conventional infrastructure teams. No OS upgrades, no host maintenance, no writing ansible, no baking AMIs, etc.
It has a cost, but it’s baffling to say “there’s nothing of value here”. It’s a force multiplier that lets small teams grow to virtually unlimited size using identical tooling that is industry wide, making hiring and training easier.
After years of asking, #Heroku are finally allowing non-enterprise accounts to use Private Spaces.
I’m a firm believer that security features should be available to all, even if there’s a small cost impact. It shouldn’t require enormous contractual changes nor a 25% price uplift.
My third #emacs package is on #MELPA! Use heroku.el to as easily manage your #heroku instances, as you manage git with #magit. Transient is the most efficient interface possible! You can tail logs, run commands like bash and python, restart and promote dynos, connect to Heroku Postgres with #psql using built-in Emacs sql functionalityand more!