Open jbyrum opened 6 years ago
@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?
@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.
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?
heroku buildpacks:search
. In the future, we will only display registered buildpacks on elements.heroku.com/buildpacksRecommended naming conventions:
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: heroku-buildpack-registry-feedback@salesforce.com