Register in Buildpack Registry

[jbyrum]

My name is Jon Byrum and I’m a product manager at Heroku. Your buildpack is one of the top 200 most popular buildpacks on Heroku!

I would like to invite you to publish your buildpack early in our Buildpack Registry, before it is made available to the general public (expected early July).

To register your buildpack, visit: https://addons-next.heroku.com/buildpacks Documentation: https://devcenter.heroku.com/articles/buildpack-registry

Why register?

• By registering early you’ll be able to grab your preferred namespace for the buildpack
• After registering, your buildpack will be available to all Heroku users when they run heroku buildpacks:search. In the future, we will only display registered buildpacks on elements.heroku.com/buildpacks
• The Buildpack Registry makes it easy for you to publish a new version of your buildpack, as well as roll back if there are errors

Recommended naming conventions:

• We recommend that you use the same namespace (e.g., jbyrum) with Buildpack Registry that you use on GitHub
• In general, avoid using "buildpack" in the name of your registered buildpack
  • For example: If your Github repo is github.com/foobar/heroku-buildpack-elixir, then we recommend a name like "foobar/elixir"

It would be greatly appreciated if you could publish before June 18th, as we prepare to make the feature publicly available. Registering a buildpack should take approximately 5 minutes.

If you have any questions about registering (or run into any issues), please email: [email protected]

[cantino]

I appreciate the offer, but I'm not willing to grant Heroku access to read and write to all of my private repositories.