Could not find "rebar3" when starting process about heroku-buildpack-elixir HOT 6 CLOSED

Right, found what the actual problem is — the Procfile was recently changed from web: mix phoenix.server to web: MIX_ENV=prod mix phoenix.server. The server should be using the same MIX_ENV as the one used to compile the dependencies. Closing the issue 👍

from heroku-buildpack-elixir.

Looks like the problem was that I was setting MIX_ENV to staging (for which I have a staging.exs config file with a different host name) on that Heroku account; changing that to prod solved the problem and the dyno kicked the server running again.

Is there a workaround to making this work on Heroku with a MIX_ENV other than prod?

from heroku-buildpack-elixir.

It sounds weird that setting MIX_ENV would be related to rebar being missing, I think there's another issue here. I run applications with MIX_ENV=staging without issues.

from heroku-buildpack-elixir.

Agree — the app was working before on staging, so I'm not sure what exactly have changed. I filed a ticket on Heroku and unfortunately they said this was out of their scope of support; but the support person did point out the difference in the _build folder (staging vs prod between my staging and production applications), which led me to changing the MIX_ENV value on staging.

Before doing that, I tried creating a new Heroku account from scratch with identical ENV variables to the staging one (including MIX_ENV=staging) — deploying the app on the new account resulted in the same error.

from heroku-buildpack-elixir.

@svileng did you use the "Promote" feature in Heroku to release your app to production? I am facing the same issue after I've created the staging env. So basically, my app has a staging app with MIX_ENV=staging and when I promote it to prod, I get that rebar3 error message.

from heroku-buildpack-elixir.

@jorbs Sorry but I cannot remember, I can see this is from 2016, and my memory is not that good 😄

from heroku-buildpack-elixir.