# django-deployment Use Fabric and Chef-Solo to manage deployment
Start by defining the information for your server. You can do this perhaps in local_settings.py or settings.py.
from fabric.api import env env.hosts = [“server_ip”] env.user = “user” env.password = “password”
There are a bunch of templates that can be overriden to configure deployment. During the deployment process, these files are generated and sent up to the server, so Chef can use them. We use Django inheritance, so any changes you make will be picked up.
deployment/local_settings.py.erb
deployment/logrotate.erb
deployment/nginx.conf.erb
deployment/run_celery.sh.erb
deployment/run_gunicorn.sh.erb
deployment/upstart_celery.conf.erb
deployment/upstart_gunicorn.conf.erb
1 maintainer
Metadata
1 maintainer
Release files for django-deployment 0.1.4.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| django-deployment-0.1.4.5.tar.gz | 12.9 kB | Details |
Release files / django-deployment-0.1.4.5.tar.gz
| Download URL | django-deployment-0.1.4.5.tar.gz |
|---|---|
| Size | 12.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b8f51cb6c9a9295b7af51be93f134234cda09f5fc12e3f8da1c282850f57380f
|
|
BLAKE2b-256 checksum How to use checksums |
c2593ad41537a7dc80c36bd04e80cb854b4ccb97b998e641b120b4f5d910396d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
