-
Notifications
You must be signed in to change notification settings - Fork 155
Expose buildpack detection as a command #1622
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
base: master
Are you sure you want to change the base?
Conversation
Yeah I feel like the part that checks out the repo should be separate from here, can you make that change? |
e29063e
to
cc46ea3
Compare
Cleared that out and also added handling json output when multiple buildpacks are detected. Would you like me to add the relevant functionality to utilize this in the core buildpacks plugin? Or would you rather I create a separate plugin? |
It might be useful to add "url", "slug" (eg. "heroku/ruby") or even "version" (eg. "v321") to the json output, but I am not sure how to get these. If that makes sense, do you have any suggestions I can look into? |
I'd actually rather not have this tool expose json output. Mind removing that? The detected buildpack will be in the buildpack-url and the buildpack-version file: https://github.com/gliderlabs/herokuish/blob/master/buildpacks/buildpack-clojure/buildpack-url https://github.com/gliderlabs/herokuish/blob/master/buildpacks/buildpack-clojure/buildpack-version |
b0dc8a3
to
3a94afd
Compare
Cleared that up as well. It was optional and nice-to-have really, but I get it. Let me know if you'd rather have this functionality utilized in the core "buildpacks" dokku plugin (so we can run Thanks for the comments. |
Mind adding a test for this functionality? |
I am working on a feature and want to be able to call this via dokku. Ideally
dokku buildpacks:detect app_name
, alternatively via a custom plugin. Let me know which one would make more sense.Basically just needs to run something like this:
If this is moved into buildpacks (or a separate) plugin, then the part that checks out a potential bare git repo, could probably be moved there as well and just run before the command above. Not sure about permissions complications.