Hacker News new | ask | show | jobs
by theanonymousone 570 days ago
I used these so called "build packs" a lot and owe Heroku a great deal in general.

However, when I was "forced to" use Docker containers instead of custom build packs (Heroku also supports them), I didn't look back: It's a non-vendor-locked, portable, industry standard, which works with every framework of my choice, not just Django and Spring Boot. It also doesn't need an extra effort to support.Net, or anything else for that matter.

1 comments

Cloud Native Buildpacks now produce OCI images. Here’s a tutorial for using them locally https://github.com/heroku/buildpacks/blob/main/docs/ruby/REA...
Yes. I mentioned that Heroku also supports them.
There’s a difference between classic “buildpacks” and “cloud native buildpacks” today you cannot use “cloud native buildpacks” on Heroku, but you can sign up for our pilot platform called Fir that will support them.

The “classic” buildpacks cannot natively produce docker images but CNBs can https://devcenter.heroku.com/articles/buildpacks.