Re:Defence Against the Docker Arts
by kevinsimper on Wednesday April 03, 2019 @04:01PM
(#19566753)
I like they way they highlight that combining Ruby and nodejs makes for a complicated Dockerfile, while their example after only includes Ruby and not nodejs. And do they propose a buildpack called ruby-nodejs, because in many cases you don't need nodejs in your Ruby app. OMG now buildpack's are a leaky abstraction!
[ Parent
| on HN ]
Re:Defence Against the Docker Arts
by codefinger on Wednesday April 03, 2019 @10:14PM
(#19568810)
The Ruby buildpack shown in the example installs Node.js for you. A developer doesn’t even need to be aware that it’s required to precompile assets.
Re:Defence Against the Docker Arts
by molszanski on Wednesday April 03, 2019 @05:19PM
(#19567348)
If only we lived in a universe where there was an easy to find and ready to use dockerpack ruby-node. Oh wait.
Re:Defence Against the Docker Arts
by jacques_chester on Wednesday April 03, 2019 @08:55PM
(#19568500)
The CNB design allows buildpacks to opt in or out as a group. So the same nodejs buildpack can work in multiple usecases. With ruby, java, whatever's necessary.