set a different api key for local development. #27
Conversation
This file contains hidden or 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
export-mike
added a commit
that referenced
this pull request
Jan 8, 2016
set a different api key for local development.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hi!
I've added a switch in the head.html to ensure we only set the live api key when published to github.io, to prevent any events caused in development are not stored in the segment.io dashboard. (homepage project). We now have a new project (homepage-local-development) and a different write key.
The jekyll.environment is set to true by github pages as seen here: http://mikeljames.github.io/
see changes: export-mike/mikeljames.github.io@d73f6b1
I used a personal github pages to test this out.