Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Allow main package to be at non-root path of app #2
It was not possible to build an application if it had a main package that was not in the root of the workspace. This PR creates an environment variable which will allow users to set a path.
Introduces BP_APP_MAIN_PATH environmental variable
Sorry for the delay! We're still working on Tracker integration for the new buildpacks.
I think we'd like this to be configurable via a
gomod: paths: ["some/cmd/here", "another/cmd/overhere"]
That makes sense. I think we should also support multiple targets in the same image as well (e.g., for extra binaries for DB migrations, debug tools, etc.). The v2 version of the buildpack support multiple targets via
We're trying to capture all of the build configuration in buildpack.yml and only introduce environment variables where parameters could reasonably vary across builds. I agree that this is one of those cases -- I should have considered that in my previous comment.
How about we support a default set of targets in buildpack.yml:
go-mod: targets: ["some/cmd/here", "another/cmd/overhere"]
As well as an environment variable to override that set: