Updated README file #53
Open
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
fixed sub-sub heading underlines which broke GitHub rendering
Minor correction picked up by reviewer.
corrected rst formatting; moved footnote to foot.
Closed
|
Awesome. I also thought that the README could use a bit more detail and was thinking about adding to it, but you beat me to it! :-) I hope this is merged. Well done! |
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.
This replaces PR #51 #51 which was from the wrong branch in this fork. This also adds additional notes regarding enabling proxying to upstream indexes.
The original comment for PR 51:
In installing djangopypi for the first time I found that the README was not sufficiently complete for new users. Whilst I could see what was required get get package upload and download working, it could slow down others or cause them to give up.
I have therefore added to the README file in a way that I think helps.