go: command not found about heroku-buildpack-go

[pemistahl]

I just stumbled over the same problem. The command in your Procfile is wrong. Instead of writing web: go run main.go you need to enter web: /bin/your-app-name. The app name is equivalent to the name of your git repository.

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.

[mble]

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.

[acamara2016]

I'm still experiencing this issue, the docs is not really clear on how to write your Procfile to run the go server.

[mble]

@acamara2016 Apologies for the difficulties - the Procfile should map a "process type" e.g. web to a command executing the binary post compile, 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 main packages (e.g. in a cmd/server, cmd/worker style setup) you would adjust your go.mod to include additional directives, such as:

// +heroku install ./cmd/server ./cmd/worker

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.