I don't use a setup.py for my _project_ deployment, but I do have a setup.py for each of the apps that I use within a project (or at least those that are 'reusable')
For project deployment, I use a fabfile that does the following: * installs public keys onto the server (if necessary) * creates the directory structure required (if necessary) * copies the project onto the server * installs requirements from REQUIREMENTS.txt * runs collectstatic, migrate, etc * restarts the web server (apache/nginx/whatever). So, I can do: $ fab deploy --host production.server I can do each of these parts separately, if necessary, or the whole lot. I also have a wrapper around django-admin.py: $ fab django:collectstatic --host server And one around web server restart: $ fab apache:graceful --host server Matt. -- You received this message because you are subscribed to the Google Groups "Django users" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/QLWwo6y_fV8J. 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.
