Jan Dittberner
ea3164b762
- move settings to gvafile.settings - use gvafile.settings directly without Django support - initialize Celery without Django - remove Django requirements
48 lines
862 B
ReStructuredText
48 lines
862 B
ReStructuredText
==================
|
|
Code documentation
|
|
==================
|
|
|
|
gvafile is implemented as a set of `Celery`_ tasks.
|
|
|
|
.. _Celery: http://www.celeryproject.org/
|
|
|
|
|
|
The project module :py:mod:`gvafile`
|
|
====================================
|
|
|
|
.. automodule:: gvafile
|
|
|
|
|
|
:py:mod:`celery <gvafile.celery>`
|
|
---------------------------------
|
|
|
|
.. automodule:: gvafile.celery
|
|
:members:
|
|
|
|
|
|
:py:mod:`exceptions <gvafile.exceptions>`
|
|
-----------------------------------------
|
|
|
|
.. automodule:: gvafile.exceptions
|
|
|
|
|
|
:py:mod:`settings <gvafile.settings>`
|
|
-------------------------------------
|
|
|
|
.. automodule:: gvafile.settings
|
|
:members:
|
|
|
|
|
|
:py:mod:`filservertasks` app
|
|
============================
|
|
|
|
.. automodule:: fileservertasks
|
|
|
|
|
|
:py:mod:`tasks <fileservertasks.tasks>`
|
|
---------------------------------------
|
|
|
|
.. automodule:: fileservertasks.tasks
|
|
:members:
|
|
:undoc-members:
|