4 ms·
Does this use Heroku buildpacks or do they reinvent the wheel? Edit: Otto appears to do a lot of things. But the part that everybody's complaining about is th
by bryanlarsen 11y ago
Does this use Heroku buildpacks or do they reinvent the wheel?
Edit: Otto appears to do a lot of things. But the part that everybody's complaining about is the "magic" part, the part that sets up a system automatically based on the language of the app. Heroku buildpacks also perform this magic, and have been open sourced and have a large community that helps maintain them. They're useful outside of Heroku -- for instance you can use them with docker via https://github.com/progrium/buildstep https://github.com/progrium/buildstep
It seems crazy to me that Hashicorp would try and reinvent this wheel. It's a problem that's fairly easy to do as a proof of concept, but it's the niggling details and number of combinations that can really explode.
- ldpg 11y agoIn that analogy Heroku buildpacks are more like the boot the police put on your car.
- jacques_chester 11y agoI've worked on Cloud Foundry buildpacks team. Several of Cloud Foundry's default are downstream from Heroku (Ruby, Python, NodeJS) and several aren't (Java, Go, PHP). Heroku's buildpacks are open, but they build them for their own purposes. In particular a large part of my work involved recreating behaviours added to support this or that Heroku change (particularly STACK, god what a mess that was), dealing with binaries being silently substituted, the messy statefulness of their staging architecture. Oh, and most importantly, we made it all work in a disconnected environment. Which Heroku never intended. Speaking individually, not as a Pivot, if you didn't have to, I wouldn't recommend starting with Heroku's buildpacks. They solve a lot of problems, but no small part is solving Heroku's problems.
- cfthrowaway 11y agoIt's interesting you say that, because Cloud Foundry recently built a requirement for the environment that runs in their Warden containers (https://github.com/cloudfoundry/stacks https://github.com/cloudfoundry/stacks) into their buildpacks, which caused applications on CF distributions that used other stacks to break when using their buildpacks.
- jacques_chester 11y agoI was partly responsible for that work. We did it for the same reason as Heroku: Ubuntu 10.04 passed out of LTS. CF buildpacks explicitly state which binaries should be used with which stack in the manifest.yml file. If you had a breakage, feel free to report it on the relevant github repo.
- deleted 11y ago[deleted]