Blog entry backend improvements #15
Merged
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
|
|
||
| # PyCharm project files | ||
| .idea/* |
There was a problem hiding this comment.
Generally stuff like this ought to go in your own .git/info/exclude, or you should configure your tools not to put random stuff in the project directory (e.g. setting PIP_LOG or whathaveyou).
|
Remember to run ./manage.py migrate blog 0001 --fake |
|
... and deployed. Thanks! |
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.
Russell loves raw HTML a lot but he thought that maybe others would prefer using reStructuredText to write blog entries, so I did that :-)
Admins can now also preview an entry's draft before it gets published.
I've added some South migrations to convert the existing database. I recommend you to try it on a dummy database first to be sure that the functionality works as you expect.