Hi HN . This is my post. Somewhat surprised to see it on the front page.
This post was written for an in person hackday for RubyConf, but it links out to some async tutorials for using Cloud Native Buildpacks like these ones that are programmatically generated to guarantee consistency and correctness. https://github.com/heroku/buildpacks/tree/main/docs#use
Since that event, we’ve added 8 tutorials for using CNBs with .NET, Go, Java (Gradle), Java (Maven), Node.JS, PHP, Python, Ruby, and Scala.
Let me know if you’ve got questions on either using a CNB to build an OCI image or anything about libcnb.rs or our Rust stack for buildpack development.
Thank you for your long time work in Ruby comunity <3
You are welcome!
The event yielded a few commits to the Ruby CNB, but none to any other deploy or build tools.
I left my session open ended and that resulted in a fix to a surprisingly difficult to debug problem in syntax suggest (runtime syntax parsing error tool I maintain). Thanks to Andy for pairing with me on it over the session https://github.com/ruby/syntax_suggest/pull/232.
Overall the in-person hackday was long, but fun and rewarding.
Nice to Know: Buildpacks are also usable with Cloud Foundry - an enterprise grade open source PaaS which is used by a lot of large corporations.
Can I ask buildpack to give me a Dockerfile that I can use/edit later?
You could write this whole article with `s/cloud native//` and none of its meaning would change. Cloud native is meaningless.
There’s a whole other “buildpack” system that is now retroactively called “classic buildpacks” https://devcenter.heroku.com/articles/buildpacks#classic-bui...
Calling it a “Cloud Native Buildpack” differentiates between the two ecosystems. The CNB project is an open spec and part of the CNCF.
It's literally part of the name of the technology. https://buildpacks.io/