Output configuration after calling configure command #283
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
$ exercism configure --key=abc123
Configuration written to /Users/kytrinyx/.exercism.json
--key=abc123
--dir=/Users/kytrinyx/exercism
--host=http://localhost:4567
--api=http://x.exercism.io
By extension this will also give you your current config values if you
call configure without any flags. It's faster than the debug command
(because of the latency checks), and it's useful during development
when you might be talking to a local version of the app in one moment
and then need to switch to the production version the next.
|
👍 ✨ |
Tonkpils
added a commit
that referenced
this pull request
Jan 26, 2016
Output configuration after calling configure command
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.
By extension this will also give you your current config values if you
call configure without any flags. It's faster than the debug command
(because of the latency checks), and it's useful during development
when you might be talking to a local version of the app in one moment
and then need to switch to the production version the next.