# django-fly It is an <b>useful command line tool</b> to manage (initialize and update) the deploy settings with <b>NGINX, Supervisor, Gunicorn, Letsencrypt</b> in the Linux web server. Current version only fits django 2.2.x.
It is my personal-used command to deploy django web app.
## Installation `$ pip3 install django-fly`
If you are failed to do pip3 install, please git clone this repo, then `python3 setup.py install`.
## Usage #### 1. `$ django-fly init`
To initialize the __deploy__ directory and sample configurations.
#### 2. `$ django-fly update`
After modificating and moving setting files under the right section under the __deploy__ directory, you can use this command to update settings of NGINX and Supervisor.
Metadata
Release files for django-fly 0.0.4
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-fly-0.0.4.tar.gz | 3.2 kB | Without provenance | Details for django-fly-0.0.4.tar.gz |
Release files / django-fly-0.0.4.tar.gz
| Download URL | django-fly-0.0.4.tar.gz |
|---|---|
| Size | 3.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
838f9701a21b67015907033cf21223ef8c147aeba5a478893d388817b822d6d1
|
|
BLAKE2b-256 checksum How to use checksums |
b907d71a9fddf27055973bfaea8378c91a392930b90fb44bdfcb2b80a859c172
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.6.1 requests/2.25.0 setuptools/50.3.2 requests-toolbelt/0.9.1 tqdm/4.51.0 CPython/3.9.0
|
Security for django-fly 0.0.4
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.