3 ms·
If you're like me and make golang apps with private packages on GitHub, you're going to have a bad time deploying to Heroku. This is because the heroku buildpa
by pearkes 13y ago
If you're like me and make golang apps with private packages on GitHub, you're going to have a bad time deploying to Heroku.
This is because the heroku buildpack for go has to `go get github.com/user/private-repo` the necessary packages. Public repos work fine for this, but private repos need credentials. There's a few reasons this isn't easy on Heroku.
I ended up working around it[1] but am still not happy with the security implications.
[1] https://github.com/kr/heroku-buildpack-go/issues/17#issuecomment-21213899 https://github.com/kr/heroku-buildpack-go/issues/17#issuecom...
- pjvds 13y agoThis is an interesting scenario. I've resolved this by running the entire build pipeline on wercker and only deploy the binary on Heroku by using the null buildpack. I'll write up a post on this in the coming days.
- miesie 13y agobtw you can find the Heroku null buildpack to launch binaries on Heroku here: https://github.com/ryandotsmith/null-buildpack https://github.com/ryandotsmith/null-buildpack