3 ms·
Cartage looks neat (thought Googling it took a few tries). To me it "looks" like a buildpack, insofar as you are taking something, injecting its dependencies a
by jacques_chester 10y ago
Cartage looks neat (thought Googling it took a few tries).
To me it "looks" like a buildpack, insofar as you are taking something, injecting its dependencies and producing an artifact that's ready to run by itself. If you ever whack bin/detect, bin/compile and bin/release onto it, it'll probably work well enough as a buildpack in connected environments.
- halostatue 10y agoThanks. We’re going to add Node, Lua, and Elixir plug-ins soon to enable standalone running. The nice thing about making just a tarball at the end of the process is that it should be relatively easy to make anything else (Docker image, AMI, etc.) with that. https://github.com/crohr/pkgr https://github.com/crohr/pkgr is the only thing that’s nearly similar, and it does a few things differently than Cartage (https://github.com/KineticCafe/cartage https://github.com/KineticCafe/cartage for anyone else following this subthread). Pkgr is a little more opinionated on using the OS environment and making sure that OS-level dependencies are fully declared…I leave that to Ansible, for the most part.
- jacques_chester 10y agoIf you had an option to package the runtime, you could use the binary buildpack[0] to run Cartage tarballs. [0] https://github.com/cloudfoundry/binary-buildpack https://github.com/cloudfoundry/binary-buildpack