I use pip and virtualenv for reproducible environments, nginx and gunicorn as production web servers, init.d scripts (on debian) for managing gunicorn (and just about everything other important process on the server), mercurial for source control and fabric for deployment. I keep all files necessary for deployment in the project directory (and therefore in source control) so that they stay together. This includes templates for nginx configuration and the init script, since I use fabric for both initial deployment and all subsequent updates.
I have three separate settings files for deployment, test, and production. They don't import from each other yet, but that would be much better (thanks John). Fabric symlinks settings.py to whichever one is appropriate for the environment. My fabric file has separate functions for test and production which just set some fabric environment variables (domain, IP, etc.). This setup has worked well thus far. In the future I'd like to have the settings, fabfiles, nginx and init script templates all import common settings from some central place. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
