Hey guys, I'm looking for deployment best practices for Django projects. Google searches seem to show countless numbers of them, many of them somewhat contradictory :-)
So as a simple discussion point: I'm curious to know if lots of people use setup.py to deploy a django project? That'd mean setup.py would install your python packages to somewhere on sys.path, maybe in your python site-packages or maybe in a virtualenv. Is this considered a common/recommended practice? If so -- where do you put your settings files? Maybe you want settings files in /etc/myproject? and add that to sys.path? Do people do this? Or do people skip the setup.py thing, and just check out their source to some directory and add that directory to sys.path? What I'm doing at the moment: - Fabric command sets up apache and directories - Another one uses setup.py to create an archive, delivers the archive and runs setup.py install etc. Is this silly? What are your thoughts? -- Tom Eastman // Catalyst IT Ltd. // +64 4 803 2432
signature.asc
Description: OpenPGP digital signature
