No Go in Heroku environment

[Joel Feinstein]

Looks like the 'go run goose_main.go ...' command fails on Heroku because Go isn't found in the bin path. Is there a workaround?

[Anton Holmquist]

I get this error too. I'm using go-style migrations instead of sql. Any solution to this?

$ heroku run goose -env production up
Running `goose -env production up` attached to terminal... up, run.5939
goose: migrating db environment 'production', current version: 0, target: 20141012220956
`go run` failed: exec: "go": executable file not found in $PATH

[Joel Feinstein]

I got around it by migrating the remote production database from a local installation of goose.

[Anton Holmquist]

I didn't think of that. That's probably a better option anyway, I guess. Thank you.

[Joel Feinstein]

I'm still fiddling with how best to determine DATABASE_URL on a local machine. The suggested method of installing goose on Heroku (i.e. 'import _ ...') doesn't seem to play well with Godep (which I don't like either), so like you said, I think it's better not to install goose on Heroku.