|
|
|
|
|
|
by nailer
2818 days ago
|
|
|
Non vendor answer: It's a script. It might use packages, it might not. It builds a box with whatever runtime is necessary to run your app. It's not a new technology. The resultant image could be a container or any other kind of imaging format. Here's the node one. It's a shell script. It sets up node. You probably already had it before you knew what a build pack was: https://github.com/buildpack/samples/blob/master/nodejs-buil... |
|
|
A current v2b NodeJS buildpack can be found here: https://github.com/cloudfoundry/nodejs-buildpack
A current work-in-progress Java buildpack: https://github.com/projectriff/riff-buildpack
I've worked on Buildpacks fulltime twice now for Pivotal.
I've seen things you people wouldn't believe. Package systems on fire off the shoulder of Orion. I watched C-compilers glitter in the dark near the obscure Nokogiri-interacting-with-stray-environment-variables-if-you're-using-a-slightly-too-old-SQLite-and-the-symlink-is-broken-due-to-an-upstream-bug-that-wasn't-fixed-because-nobody-realised-this-would-happen gate.
But unlike the shell script, these moments will not be lost in time like rain. They will be shipped reliably, repeatably into production by two professional organisations prepared to assign more than a dozen engineers, watch hundreds of upstream dependencies, invest in millions of dollars of automation, test against thousands of distinct applications with tens of thousands of running containers serving billions of requests per day across multiple customers in multiple countries.
I invite you to maintain a nodejs buildpack yourself. Prove us all wrong.