# Django Deployement Tools
Tools to help deploy a django application.
## INSTALLATION:
pip install Django-Deployment-Tools
## CONFIGURATION:
Add ‘django_deploy_tools’, in your settings.INSTALLED_APPS.
Add a STATIC_ROOT variable in your django settings.py file.
See <https://docs.djangoproject.com/en/3.0/ref/settings/#static-files>, <https://docs.djangoproject.com/en/3.0/ref/settings/#static-root> and <https://docs.djangoproject.com/en/3.0/howto/static-files/> for more details.
## USAGE:
First collect static files:
python manage.py collectstatic
If you have django-compressor (optional) run:
python manage.py compress
(see <https://django-compressor.readthedocs.io/en/stable/> for more details).
Then, create a wsgi file:
python manage.py make_sgi –wsgi –out path/to/wsgi_file
And then generate an apache configuration file:
python manage.py make_apache_conf –wsgi path/to/wsgi_file –sll –out /path/to/apache_conf_file
For more information check :
python manage.py make_apache_conf -h
Especially to define the proper ssl certificates. If not specified when creating the configuration file you will have to edit the generated apache configuration.
## DEVELOPMENT:
If you want to contribute, deployement commands are to be added in the
management/commands directory: <https://github.com/ygbourhis/django_deploy_tools/tree/master/django_deploy_tools/management/commands> As per the django documentation: <https://docs.djangoproject.com/en/dev/howto/custom-management-commands/> And configuration templates used by the commands are put in the templates/django_deploy_tools`directory: <https://github.com/ygbourhis/django_deploy_tools/tree/master/django_deploy_tools/templates/django_deploy_tools> Then, before adding a pull request, run the `check_code script to check coding rules
TODO: Add unittests.
Metadata
Release files for Django-Deployment-Tools 0.5.0
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 | Actions |
|---|---|---|---|---|
| Django Deployment Tools-0.5.0.tar.gz | 16.9 kB | Without provenance | Details for Django Deployment Tools-0.5.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| Django_Deployment_Tools-0.5.0-py3-none-any.whl | Python 3 | none | any | Details for Django_Deployment_Tools-0.5.0-py3-none-any.whl |
Total release size: 34.1 kB
Release files / Django Deployment Tools-0.5.0.tar.gz
| Download URL | Django Deployment Tools-0.5.0.tar.gz |
|---|---|
| Size | 16.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2104ba27dd6cf77f5aa997feb33be97d3023e6fa4863665988b8fc587211f899
|
|
BLAKE2b-256 checksum How to use checksums |
f7ac2967d856e9e4c47aefda41eb710c90ae2366355721b772215f16914fdb43
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.2.0 requests-toolbelt/0.9.1 tqdm/4.40.1 CPython/3.8.0
|
Release files / Django_Deployment_Tools-0.5.0-py3-none-any.whl
| Download URL | Django_Deployment_Tools-0.5.0-py3-none-any.whl |
|---|---|
| Size | 17.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c7370077609fee3a0002a35517b0354bbf31b4629a48e77b30ba667055a58161
|
|
BLAKE2b-256 checksum How to use checksums |
abe92a999cfc5217dd674d17ec74c37128ad0e0c307e5b03b325735485715511
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.2.0 requests-toolbelt/0.9.1 tqdm/4.40.1 CPython/3.8.0
|
Security for Django-Deployment-Tools 0.5.0
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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.