-
Notifications
You must be signed in to change notification settings - Fork 513
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
go: command not found #467
Comments
I just stumbled over the same problem. The command in your This is pretty badly documented, I must say. It took me quite some time to figure this out. The Heroku guys should improve their docs. |
Yes, we should make this clearer that the buildpack first builds your binaries and does not include a copy of the toolchain. We do explain this here https://devcenter.heroku.com/articles/go-support#runtime-behavior, but it is pretty out of the way. |
I'm still experiencing this issue, the docs is not really clear on how to write your Procfile to run the go server. |
@acamara2016 Apologies for the difficulties - the Procfile should map a "process type" e.g. web: web-server -port "${PORT}" You can see an example of this here: https://github.com/heroku/go-getting-started/blob/main/Procfile. If you have multiple
Which would then be available through something like: web: bin/server
worker: bin/worker More details in https://github.com/heroku/heroku-buildpack-go?tab=readme-ov-file#go-module-specifics. I'll look at adding a complete worked example to the docs tomorrow. |
The go command does not work even though the go build pack is applied.
version: 1.16
Below is the corresponding log.
The following is my file directory
What did I miss?
The text was updated successfully, but these errors were encountered: