=====================================
Django-documentation
=====================================
This `Django <http://djangoproject.com>`_ app has for purpose to integrate
protected sphinx based documentation .
Installation
============
Depedencies
~~~~~~~~~~~
django-documentation depends on `Sphinx <http://sphinx.pocoo.org>`_
Installing django-simple-feedback
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Install into your python path using pip::
pip install django-documentation
pip install -e git+git://github.com/Narsil/django-documentation.git#egg=django-documentation
Add *'documentation'* to your INSTALLED_APPS in settings.py::
INSTALLED_APPS = (
...
'documentation',
)
Add *'(r'^docs/', include('documentation.urls')'* to your urls::
urlpatterns = patterns( '',
....
(r'^docs/', include('documentation.urls'),
)
Settings
~~~~~~~~
Set up where is your documentation, and a function that has a user for argument
and returns **True** if user is allowed to see the doc. If you plan on using
``lambda user: True``, then you probably should not be using this app, as
staticfiles would be better suited for this task. ::
DOCUMENTATION_ROOT = '/path/to/docs/'
DOCUMENTATION_ACCESS_FUNCTION = lambda user: user.is_staff
The DOCUMENATION_ROOT is the root of your sphinx doc where the Makefile exists, if you html docs is
placed somewhere else than ``DOCUMENTATION_ROOT + '_build/html/'`` then you
can override it with::
DOCUMENTATION_HTML_ROOT = '/my/other/location/
Note that django-documentation serves the content via x-sendfile when DEBUG
is False, otherwise it uses
`django.views.static.serve <https://docs.djangoproject.com/en/dev/howto/static-files/#django.views.static.serve>`_
To override use ::
DOCUMENTATION_XSENDFILE = True
django-documentation also comes with a command goodies ::
./manage.py makedoc
to generate the documentation.
Django-documentation
=====================================
This `Django <http://djangoproject.com>`_ app has for purpose to integrate
protected sphinx based documentation .
Installation
============
Depedencies
~~~~~~~~~~~
django-documentation depends on `Sphinx <http://sphinx.pocoo.org>`_
Installing django-simple-feedback
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Install into your python path using pip::
pip install django-documentation
pip install -e git+git://github.com/Narsil/django-documentation.git#egg=django-documentation
Add *'documentation'* to your INSTALLED_APPS in settings.py::
INSTALLED_APPS = (
...
'documentation',
)
Add *'(r'^docs/', include('documentation.urls')'* to your urls::
urlpatterns = patterns( '',
....
(r'^docs/', include('documentation.urls'),
)
Settings
~~~~~~~~
Set up where is your documentation, and a function that has a user for argument
and returns **True** if user is allowed to see the doc. If you plan on using
``lambda user: True``, then you probably should not be using this app, as
staticfiles would be better suited for this task. ::
DOCUMENTATION_ROOT = '/path/to/docs/'
DOCUMENTATION_ACCESS_FUNCTION = lambda user: user.is_staff
The DOCUMENATION_ROOT is the root of your sphinx doc where the Makefile exists, if you html docs is
placed somewhere else than ``DOCUMENTATION_ROOT + '_build/html/'`` then you
can override it with::
DOCUMENTATION_HTML_ROOT = '/my/other/location/
Note that django-documentation serves the content via x-sendfile when DEBUG
is False, otherwise it uses
`django.views.static.serve <https://docs.djangoproject.com/en/dev/howto/static-files/#django.views.static.serve>`_
To override use ::
DOCUMENTATION_XSENDFILE = True
django-documentation also comes with a command goodies ::
./manage.py makedoc
to generate the documentation.
Metadata
Release files for django-documentation 1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| django-documentation-1.1.tar.gz | 6.1 kB | Without provenance | Details |
Release files / django-documentation-1.1.tar.gz
| Download URL | django-documentation-1.1.tar.gz |
|---|---|
| Size | 6.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4da3ddf19ce5f987fd483a1d7277c09faf02686d5a73c6f16c910f9df8e23624
|
|
BLAKE2b-256 checksum How to use checksums |
62e2490b52d6751538017edf7bfa8fd13edf37f0ac01a8a348654a3b0dcc2e78
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-documentation 1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.