djangodeployer
Deploy django project with nginx, gunicorn, supervisor, postgresql on debian.
Quick start
Creates the basic config file.
djangodeployer init
Edit the basic configuration dj_config.json.
{
"IP_ADDRESS": "0.0.0.0", # server public ip address
"SERVER_NAME": "django-server", # hostname of the server
"LINUX_USER": "dj", # server username
"DJ_PROJ": "djangosite", # django project name
"PG_USER": "djadmin", # postgresql database username
"PG_DB": "djangodb", # postgresql database name
"DOMAIN_NAME": "mywebsite.com" # domain name
}
Deploy with the command:
djangodeployer deploy
Requirements
- Python3.6+
Installation
python3 -m pip install djangodeployer
Acknowledgments
Most of the functions use the code from Corey Schafer's youtube channel:
- https://www.youtube.com/watch?v=Sa_kQheCnds&t=2952s
- https://www.youtube.com/watch?v=goToXTC96Co
- CoreyMSchafer - https://github.com/CoreyMSchafer
The code is wrapped in a python package to automate the deployment.
License
MIT
Metadata
Release files for djangodeployer 0.1.2
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 |
|---|---|---|---|---|
| djangodeployer-0.1.2.tar.gz | 7.2 kB | Without provenance | Details for djangodeployer-0.1.2.tar.gz |
Release files / djangodeployer-0.1.2.tar.gz
| Download URL | djangodeployer-0.1.2.tar.gz |
|---|---|
| Size | 7.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b3222058919e2a2ab4217f39344a9bcb6ec739bdff9880445876a867f285cd74
|
|
BLAKE2b-256 checksum How to use checksums |
546142132f9ed86c7fe5d40c99a51d40062e912280c8fd865538a7941ae55a33
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.23.0 setuptools/46.1.3.post20200330 requests-toolbelt/0.9.1 tqdm/4.45.0 CPython/3.8.2
|
Security for djangodeployer 0.1.2
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.