heroku-buildpack-ruby VS hatchet

Did you find this article? https://github.com/heroku/heroku-buildpack-ruby/issues/1202

There is a Github issue on this topic in the heroku-ruby-buildpack repo with some success stories in the comment section and a hint that build-in-app-dir may become the default behaviour in the future.

For instance the way Heroku used to build apps defeated a good part of Bootsnap usefulness, actually making it slow boot time, but they fixed that recently https://github.com/heroku/heroku-buildpack-ruby/issues/979.

{ "environments": { "test": { "buildpacks": [ { "url": "https://github.com/heroku/heroku-buildpack-ruby" }, { "url": "https://github.com/heroku/heroku-buildpack-chromedriver" }, { "url": "https://github.com/heroku/heroku-buildpack-google-chrome" } ], "addons": [ "heroku-postgresql" ], "scripts": { "test-setup": "bin/rails assets:precompile", "test": "bin/rspec" } } } }

{ "env":{ "RAILS_MASTER_KEY":{ "require":true } }, "scripts":{ "postdeploy":"bin/bundle exec rake db:migrate rake db:seed" }, "addons":[ { "plan":"heroku-postgresql:free" }, { "plan":"heroku-postgresql:free", "as":"audit" }, { "plan":"rediscloud:free" }, { "plan": "rollbar:free" } ], "buildpacks":[ { "url":"https://github.com/heroku/heroku-buildpack-ruby" } ] }

This answer might help you OP, schneems says (in 2017 mind) that you need to manually define the missing assets:precompile task.

Here's some code I wrote without design for testability: https://github.com/heroku/hatchet/blob/main/lib/hatchet/app.rb. It's a monster. To test it in isolation you MUST use mocks/stubs or can only be called in an integration test (slow). If I wrote this with testing in mind, you probably wouldn't have to see code like this in my tests: https://github.com/heroku/hatchet/blob/7aa774b1ae713724a84f25d37a545963f9445b37/spec/hatchet/app_spec.rb#L42-L47.