This message was deleted.

Have you checked out our example here? Its a bare bones rails app but might be of use. As for it not using

pack

, those are things we are actually experimenting with, hope to have some updates on that soon as our approach matures some.

I replied in the other thread. It seems that yarn.lock presence solves the issue I had. It just wasn't that obvious. I didn't really use modules, it was a dependency from bootstrap. I found it a bit weird that only specific rubies are supported by paketo-buildpacks, but that's irrelevant to epinio. Thanks for the suggestion!

Currently non-paketo builders aren't officially supported so it probably would not work, however we know this is a pretty major restriction and are working on adding support for more types of build packs. With all that being said I would just use paketo for now.

It's also worth input that we are evaluating moving away from the paketo buildpacks as the recommended defaults. there is lots of good Cloud Native Buildpacks project activity which we're aligning with. I also really like the idea of making the project.toml more first-class - including supporting the inline buildpacks concept