-
Notifications
You must be signed in to change notification settings - Fork 188
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
Cannot find diesel during Heroku release step #40
Comments
After trying more, if I set the buildpack to the current GitHub repo with |
There's documentation here on setting the build pack correctly: https://github.com/emk/heroku-buildpack-rust#using-this-buildpack Is this insufficient? I'd be happy to fix the instructions if we can figure out what's going wrong here! |
I had the same issue. I ran the first build without I read the documentation you are referring to but it didn't help me. |
@emk I followed the directions in the README but also had an issue with the first build. I had |
I ran into the same issue.
|
Hmm, that's odd. I'm not sure why you'd be trying to link |
@emk your comment confuses me, if you didn't intend for the diesel cli to be installed then what is this section for? https://github.com/emk/heroku-buildpack-rust#running-diesel-migrations-during-the-release-phase I check the generated |
Oh, I'm so sorry! I misunderstood. Your error was caused by the @msehnout's advice to set the following in
It looks like If somebody can confirm that this works, I can change the default setup. Thank you for any information you can provide! |
I tried just
and it didn't work. What worked was setting
and then also with
|
Same here, I took the following steps:
|
I ran into a similar issue, setting
As an aside, is there any reason the Elements package |
Hmm, do I need to take any special steps to update the Elements package, or does it just automatically use |
Not sure about the buildpack publishing, as I've never done it, but it doesn't seem to be automatic going by this notice on the docs: https://devcenter.heroku.com/articles/buildpack-registry#publishing-a-buildpack-version Seems that the convention might be to tag a commit with a version, and then you can select that for wider use. |
Ah, thank you! I'll take a look. |
the current default version wouldn't do it emk/heroku-buildpack-rust#40
Is the documentation still incomplete? Please help :)
|
Hmm, I ran the command to reinstall the buildpack and instead of saying that it was already installed I received:
Thanks to all and please add to the documentation a mention that after editing 'RustConfig' you need to run 'heroku buildpacks: set' again. Now I have a different error ( |
still unable to make it work |
This fixed it for me as well |
Ditto — looks like the command |
Hi, I think I have followed all the steps to run Diesel migrations on release with Heroku correctly but I keep getting this error in Heroku deploys:
It seems the step which is supposed to install the
diesel-cli
does not seem to run. These are myRustConfig
andProcfile
:Is there something I missed in the setup?
The text was updated successfully, but these errors were encountered: