| Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
|
|
Fixed errors in URL dispatch docs in "Using a Route Prefix to Compose Applications" section
|
|
|
|
|
|
|
|
section of the docs/narr/urldispatch.rst docs.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
name: show_settings
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Conflicts:
docs/narr/views.rst
|
|
|
|
|
|
- Fork point: master now represents a future 1.4 release.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
changes dont require a restart
|
|
server, put code reloading into its own section
|
|
convention
|
|
|
|
|
|
|
|
Keep the same vocabulary than previously in the doc
|
|
Even if this information it's not enough, when you read the doc via pdf that give you which command to use without having to jump of section. I find it better for the learning flow of the reader than jumping around.
|
|
instruction the user doesn't have more than one package which myproject
|
|
correct and generic, after following the previous step of the documentation the user would have only one package which is 'myproject'
|
|
|