-
-
Notifications
You must be signed in to change notification settings - Fork 577
Conversation
Thanks for looking into, unfortunately it doesn't solve the issue of #841. The behind that ticket is the binary that built from running Also, this line: cmd.Env = envy.Environ() breaks Windows, which is why it was removed and caused the problem of #845. When implemented #841 won't fix #845 unfortunately. |
The good news is, you're very close to the actual implementation. :) I was thinking that adding a line to the func init() {
envy.Set("GO_ENV", "<environment>")
} That's might be enough to do it. |
Should it be just |
Update bin.go Update exec.go Update build.go Update build.go change cmd.Env to whole envy.Environ instead burn GO_ENV into binary Update build.go Update options.go remove forgotten unused commit asdf
82ba3d1
to
c8750ce
Compare
@Zarkopafilis I'm closing this PR in favor of #850 because GitHub won't let me push a commit to this PR. When testing this I found that it still wasn't working. I dug deeper and found that the place that we wanted to set the ENV var was too late. The In order to get it to load properly, I moved the setting of the ENV var from the Thanks for taking point on this. |
…'s loaded before the actions package. fixes gobuffalo#841 and fixes gobuffalo#846
I want to make sure if this should be the proper way to set the development environment for the build, in order to procceed with testing & possible mistake corrections.
A new environment flag is registered and defaulted to "development".
Then, on bin.go, its passed to envy (not persisted to the underlying environment), in order to procceed to exec.go without changing function signatures.
The value is retrieved from envy and appended in the Env slice of exec.Cmd so it can be used instead of the default one on the actual command execution step.
#841