Skip to content
This repository has been archived by the owner on Apr 3, 2023. It is now read-only.

Register buildpack in Buildpack Registry #5

Open
jbyrum opened this issue May 30, 2018 · 2 comments
Open

Register buildpack in Buildpack Registry #5

jbyrum opened this issue May 30, 2018 · 2 comments

Comments

@jbyrum
Copy link

jbyrum commented May 30, 2018

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]

@salsakran
Copy link
Contributor

@jbyrum done! Thanks for the pointer.

One dumb question, we typically funnel people through the our 1-click deployment repo https://github.com/metabase/metabase-deploy and not this buildpack. How is the registry meant to work with applications that are meant to run as a single unit vs libraries or services?

@jbyrum
Copy link
Author

jbyrum commented May 31, 2018

@salsakran Thanks for the question. In the description field in the Buildpack Registry (as well as the code repo's readme), you might want to suggest the users deploy metabase from the button.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants