Updating docs for wURL, Removing rake restriction #35
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
oestrich
added a commit
that referenced
this pull request
May 22, 2012
Updating docs for wURL, Removing rake restriction
|
Probably shouldn't have had Rails.env in the task file anyways. Thanks for the docs update. |
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.
First commit is just to give mention of how the new wURL console could be generated.
Second commit pulls off the rake task definition restriction so that a dev can decide where he wants to generate docs and where he doesn't. The case we had was that we wanted to generate docs in our QA environment. I've also been on projects where we wanted docs in production so that 3rd party devs could get to them.