paketo-buildpacks / puma

Puma Cloud Native Buildpack

gcr.io/paketo-buildpacks/puma

The Puma CNB sets the start command for a given ruby application that runs on a puma server.

Integration

This CNB writes a start command, so there's currently no scenario we can imagine that you would need to require it as dependency. If a user likes to include some other functionality, it can be done independent of the Puma CNB without requiring a dependency of it.

To package this buildpack for consumption:

$ ./scripts/package.sh

This builds the buildpack's source using GOOS=linux by default. You can supply another value as the first argument to package.sh.

buildpack.yml Configurations

There are no extra configurations for this buildpack based on buildpack.yml.

puma's Issues

Upgrade to packit v2

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

Why does this buildpack fail detection if there is not a `config.ru` file in app source?

This code block here causes the buildpack to fail detection if there is no config.ru file in the app source. This feels like a weird requirement, should this actually cause detection to fail? We have removed this kind of logic from buildpacks in the past maybe we should evaluate this one as well.

Start command does not support custom port binding

The start command, bundle exec puma, doesn't support binding to a custom port. The expectation with buildpacks is that the user should be able to set $PORT and have the app bind on that port.

Puma supports binding to a custom port through the -b flag as can be seen in these docs: https://github.com/puma/puma#binding-tcp--sockets.

This buildpack fails detection if the "gem puma" line is starts with spaces in the Gemfile.

I have a Gemfile like:

source "$SOURCE" do
  gem 'rails', '~> 6.0.3', '>= 6.0.3.2'
  gem 'puma', '~> 4.1'
...
end

And this buildpack fails to detect. When I remove the spaces before gem puma in the file, the buildpack works.

Failure: Update GitHub config workflow

Update GitHub config workflow failed.

Enable Debug Logging

With the merging of RFC 27 buildpacks should respect the BP_LOG_LEVEL environment variable and allow for debugging logging.

A good example of how to minimally implement this feature can be found in Go Build.

Failure: Push Buildpackage workflow

Push Buildpackage workflow failed.

Upgrade to buildpack API v0.5

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.

Failure: Create Draft Release workflow

Create Draft Release workflow failed.

Promote this buildpack to `paketo-buildpacks`

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

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

This RFC describes the changes.