No commit activity in last 3 years
No release in over 3 years
capistrano-django-systemd provides a solid basis for common django deployment
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
 Dependencies

Runtime

 Project Readme

This is a FORK REPO

Capistrano Django

A set of tasks built ontop of Capistrano to assist with Django deployments

example config file:

set :application, 'app_name'
set :scm, :git
set :repo_url, 'git@github.com:username/repo_name.git'
set :django_settings_dir, 'app_name/settings'
set :pip_requirements, 'requirements/base.txt'
set :keep_releases, 5
set :nginx, true
set :deploy_to, '/www/app_name.com'
set :wsgi_file, 'app_name.wsgi'
set :npm_tasks, {:grunt => 'do_something', :gulp => 'something_else'}
set :stage, :production
set :django_settings, 'production'
role :web, "user@127.0.0.1"

Ordinarily, capistrano-django builds a separate virtualenv per-deploy.

If you include:

set :shared_virtualenv, true

in your configuration file, it will instead create a virtualenv in the shared_path, and symlink it into the release path. It will build it via requirements only when they differ from those of the last release.

Author: Matthew J. Morrison. Follow me on Twitter