-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pass the staging/prod build tag through a Makefile env variable #1466
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why not keep the constants and instead make the default tag be staging?
9513228
to
38ce6b8
Compare
good idea! |
Let's change the description of this PR. Otherwise I like this. Binaries built from source using our makefile will point to staging, and releases will point to production. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we update goreleaser too to the prod tag?
Let's open a PR to do that, but before merging the PR, let's check with @evankanderson on prod status - I assume that the released binaries would be used already by people working on the docs this weekend and on Monday and I wouldn't like to interrupt their flow with binaries that point to env that can't be used.
Prod is up and running. This is good to go |
Adds a a Makefile variable that sets the staging or prod env tag. Currently the variable defaults to staging, we'll switch it to prod when ready.