paketo-buildpacks / rake Goto Github PK

Create Draft Release workflow failed.

Could we look into supporting running Rake tasks during the build process? This would be particularly helpful for Rails apps that require rake tasks to be run (outside of the Rails asset pipeline) to start the app.

I'd expect, that this would allow users to define a Ruby Builder that optionally requires Rake in any server group, e.g:

[[order]]
...
  [[order.group]]
    id = "paketo-buildpacks/mri"
    version = ...
 [[order.group]]
    id = "paketo-buildpacks/bundler"
    version = ...
 [[order.group]]
    id = "paketo-buildpacks/bundle-install"
    version = ...
 [[order.group]]
    id = "paketo-buildpacks/rake"
    optional = true
    version = ...
 [[order.group]]
    id = "paketo-buildpacks/thin"
    version = ...
....

and I'd be able to build my Rails app using this builder and an env. variable specifying which Rake task to execute. Ex.

pack build rails-app -e BP_RAKE_TASKS="my:rake_task" --builder ruby-builder

Please upgrade to the latest packit v2 release to enable new features and extended support.

Push Buildpackage workflow failed.

The paketo buildpacks team is officially supporting ruby so this buildpack should be

• renamed to paketo-buildpacks/rake
• moved to the paketo-buildpacks github org.

This RFC describes the changes.

The buildpack currently uses CNB Buildpacks API v0.2, while other buildpacks in the Ruby language family, such as the Bundle Install buildpack use v0.5. The CNB spec has evolved since then, and it would be nice to have all of the language family buildpacks up to date. To take advantage of more upstream features, the buildpack should be upgraded to API v0.5.

Check out the Buildpack API release notes for each version, and also the buildpacks.io API Migration guides for information on what has changed in each API version.