push code to dev.buttonweavers.com for December 2016 release

[cgolubi1]

This is the issue for loading code onto dev for the release. The issue for deciding which pulls to bring to staging is #2133.

As features are merged into the dev codebase branch, redeploy dev.buttonweavers.com with those changes.

Generic procedures for use in deployments:

Use a checked-out copy of buttonmen-dev to find a sort order for database updates:

cd deploy/database/updates/
UPDATES="<space-separated list of DB updates>"
git log --reverse --first-parent --oneline $UPDATES
UPDATES="<space-separated list of DB updates, now in the order reported by that output>"

Database update plan:

# in the correct git working directory
git pull origin dev
cd deploy/vagrant
vagrant provision

# on the sandbox or dev VM
UPDATES="<space-separated ordered list of DB updates, as determined above>"

sudo -u mysql mkdir /tmp/pre /tmp/post
ls /tmp/pre /tmp/post
sudo -u mysql mysqldump -u root --skip-comments -T /tmp/pre buttonmen
cd /buttonmen/deploy/database/updates
for update in $UPDATES; do
  echo "APPLYING: $update"
  cat $update | mysql -u root buttonmen
done

sudo -u mysql mysqldump -u root --skip-comments -T /tmp/post buttonmen

How to diff database dumps:

diff -r --brief /tmp/pre /tmp/post

#217 is the master ticket linking all dev code pushes.

[cgolubi1]

Okay, i'm going to deploy dev now with all the above pulls.

UPDATES="02032_no_random_dead_guy_01.sql 02115_cheese_weasel.sql 01978_steven_universe_01.sql 02122_perf.sql"

Testing on virtualbox looks fine - i don't see any issues with database diffs. Going to load on the actual dev site now.

[cgolubi1]

I'm going to deploy dev now with the above pull, which should be a noop.