4 ms·
Yeah, we ship unmodified Heroku buildpacks, plus one Cloud Foundry buildpack (https://github.com/cloudfoundry/staticfile-buildpack https://github.com/cloudfound
by Titanous 10y ago
Yeah, we ship unmodified Heroku buildpacks, plus one Cloud Foundry buildpack (https://github.com/cloudfoundry/staticfile-buildpack https://github.com/cloudfoundry/staticfile-buildpack).
So far no one is using Flynn in a fully disconnected environment, and we're aware of this limitation. My take on this is that we need a replacement for buildpacks that allows for repeatable/functional builds (think Nix for app deployment).
- jacques_chester 10y agoI see, that definitely makes it easier. The Heroku code (quite reasonably) assumes 100% connectivity. One gotcha: if you are snapshotting images after building, your images are not truly reproducible. Heroku occasionally swap out the binaries. This surprised once or twice. This is one reason we wound up building all our own runtime binaries[1]. When you get to disconnected environments, look us up. We built a whole tooling, compile-extensions[2], to make it pretty close to seamless. We intercept URLs and transform their either into our URLs or local copies of the files. (edit: actually, you could just switch to the Cloud Foundry buildpacks, since they have an identical detect/compile/release cycle) I agree that buildpacks are not the super long term solution. One area being explored by engineers at Pivotal and IBM is to give a buildpack-like experience to OCI layers[3]. I'm sure they'd be happy to work with you on this as well. [1] https://github.com/cloudfoundry/binary-builder https://github.com/cloudfoundry/binary-builder [2] https://github.com/cloudfoundry/compile-extensions https://github.com/cloudfoundry/compile-extensions [3] https://www.youtube.com/watch?v=DSTT0przx4g&list=PLhuMOCWn4P9io8gtd6JSlI9--q7Gw3epW&index=47 https://www.youtube.com/watch?v=DSTT0przx4g&list=PLhuMOCWn4P...