I've started experimenting with this idea and created simple app: https://github.com/elvard/django-deploy
I would very appreciate any opinions, ideas or second thoughts. Cheers, Tom Dne pátek, 2. května 2014 19:13:30 UTC+2 Tomáš Ehrlich napsal(a): > > Hi there, > when I deploy my django projects I always run several commands after > pulling latest code from repository. I've started using setup.py few > weeks ago which adds manage.py script into $VENV/bin. > > Basicaly, I always do: > > source $VENV/bin/activate > export DJANGO_SETTINGS_MODULE=... > > git pull > python setup.py install > manage.py syncdb --noinput > manage.py migrate > manage.py collectstatic --noinput > manage.py compilemessages > > > I wrote deployment scripts in fabric, salt, ansible, but now I'm > thinking that all these 'manage.py' actions should be part of setup > script. Anytime when would I run ``python setup.py install`` > the setup script would run all defined management commands so my > environment, database and other stuff stays up to date. > > > I've found that install command can be extended: > > http://www.niteoweb.com/blog/setuptools-run-custom-code-during-install > > I haven't found any references that anyone have used this method to > deploy django project, so I'm looking for anyone who tried this > approach before. > > > Thanks in advance > > Cheers, > Tom > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/30a7b284-38aa-4f8d-86f2-603498e5fbb2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
