scipy-conference/SciPy-2014 — pull request #40 by codersquid (2014-01-23 14:56:41+00:00)
Title: Adds provisioning fabric tasks with a few additional changes

I need a review and consensus before accepting this pull request.
* I've moved templates in to a subdirectory, it's a preference and not required.
* I've added a dependency to fabtools. It's a preference and I could rewrite things not to use it.
* I've made a hard coded change to env.hosts, when I would prefer it not to work that way. It was like this before, so I wouldn't cringe if it were committed, but ultimately we should figure out how to do this properly.
* I'm willing to add a vagrant file finally since calling fab provision can work with it
* I want to work out how to have the fabric script populate the local ip address in the nginx file so we can enable the status functionality
* We need to change the nginx file to work with .scipy.org so it will match any incoming pattern foo.scipy.org but I'm uncertain how to handle the https redirect
* I am uncertain as to whether I want to provision collectd or not -- and I've left out the nginx plugin config until we work out the nginx config

Questions
* We have dependencies in requirements.txt now that are only there for using the fab stuff -- is this a common practice for django projects or should we have a separate requirements file only intended for doing deployment things?

Finally

* I can't accurately test this since I don't have a way to provision the certs. Can you test this for me?