| 1 |
=================== |
| 2 |
Deploying GeoDjango |
| 3 |
=================== |
| 4 |
|
| 5 |
Basically, the deployment of a GeoDjango application is not different from |
| 6 |
the deployment of a normal Django application. Please consult Django's |
| 7 |
:doc:`deployment documentation </howto/deployment/index>`. |
| 8 |
|
| 9 |
.. warning:: |
| 10 |
|
| 11 |
GeoDjango uses the GDAL geospatial library which is |
| 12 |
not thread safe at this time. Thus, it is *highly* recommended |
| 13 |
to not use threading when deploying -- in other words, use an |
| 14 |
appropriate configuration of Apache. |
| 15 |
|
| 16 |
For example, when configuring your application with ``mod_wsgi``, |
| 17 |
set the ``WSGIDaemonProcess`` attribute ``threads`` to ``1``, unless |
| 18 |
Apache may crash when running your GeoDjango application. Increase the |
| 19 |
number of ``processes`` instead. |