-
Notifications
You must be signed in to change notification settings - Fork 308
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
Export PATH to erl/elixir/hex for multi-buildpack scenario #73
Comments
A pull request would be appreciated. |
Burgestrand
added a commit
to Burgestrand/heroku-buildpack-elixir
that referenced
this issue
May 2, 2016
Burgestrand
added a commit
to Burgestrand/heroku-buildpack-elixir
that referenced
this issue
May 2, 2016
Burgestrand
added a commit
to Burgestrand/heroku-buildpack-elixir
that referenced
this issue
May 2, 2016
Burgestrand
added a commit
to Burgestrand/heroku-buildpack-elixir
that referenced
this issue
May 2, 2016
Hah, wow, every amend creates its own reference to this issue. Sorry about that! |
I've opened a PR, so I'm closing this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This would allow heroku-buildpack-elixir to be used in a multi-buildpack scenario: https://devcenter.heroku.com/articles/buildpack-api#composing-multiple-buildpacks
It's probably a good idea to also export
MIX_ENV
.The text was updated successfully, but these errors were encountered: