This repository has been archived by the owner on Jul 5, 2023. It is now read-only.
Update how we set the environment to production, for segment tracking #263
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…. Default 'development'
jescalan
approved these changes
Apr 27, 2018
jescalan
approved these changes
Apr 27, 2018
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Default to
development, which should always use the dev key from middleman helpers. Any value forDEPLOY_ENVwill have that affect too, but thought it good to be explicit. Only a value ofproductionwill result in the production key.This fixes an issue we have right now, where the development key is being used and data is being sent and registered as Development traffic and not Production traffic.