Document and set up generalized deployment

[shippy]

Right now, deployment is a black box that only few understand, and I'm sick of reading about everyone deploying all the time. As our test suite, continuous integration and in-production monitoring get better, I think we should work towards the ability to deploy (a) often, (b) comfortably, (c) simply and (d) without bothering Michael Dunlap all the time.

2014/11/11

Deployment:

• Compile list of configuration parameters
• Move configuration parameters into secrets.yml with ENV calls for production
  • now I'm not sure about this, we might just want to call ENV directly...
• Install dotenv-deployment in the production and staging groups
• Test deploy.rb
• Add wiki page
• Update README instructions

Logistics:

• Talk to Michael about syncing DEV instance databases
• Figure out new deployment script structure (maybe still use Capistrano?)
• Figure out changes necessary to Jenkins script
• Should we be resetting the secret key every time? (probably not)

[orenyk]

You beat me to it! Let's make this the main issue for documentation and add deployment adjustments/fixes as new issues as they come up.

[orenyk]

This is critical in order for us to implement the Heroku button and export this app effectively. I've documented the Yale deployment process fairly well in my presentation, but we need to extract from the deployment script a generalized set of deployment instructions. Moving to v4.2, will start discussions with Mike to figure out what needs to happen.

[orenyk]

There has been a lot of discussion about this in the PR for party foul (#770) since I removed an outdated Capistrano deployment script in that branch. We should ultimately offer a generalized deployment strategy using some standard tool for future clients and that script can serve as a starting point for that work. Until then, as I said in the other conversation, I'd rather have no script than a broken one.