Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Register in buildpack registry #1

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

Register in buildpack registry #1

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]

@joewoodhouse
Copy link

@jbyrum One issue I find with this build package, from the perspective of someone that manages a large monorepo that contains a number of apps that we deploy to heroku, is that pushing any commit to our repository would cause all applications to redeploy. Which is obviously not ideal.

Is there any plans for heroku to natively support a simple system of linking an app to a subtree of a git repository?

@TheoMer
Copy link

TheoMer commented Apr 30, 2020

pushing any commit to our repository would cause all applications to redeploy. Which is obviously not ideal

@jbyrum I am experiencing the very same issue as mentioned above by @joewoodhouse. Are there any plans to enable a simple system of linking an app to a subtree of a git repository?

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

No branches or pull requests

3 participants