The database setup issue(s) should be fixed as of https://github.com/codeforamerica/councilmatic/commit/a3f7b1d9f1e0fd66a3f0f64016302fab70ed936f . There is a hook that creates a Subscriber whenever a User is created, but when first doing syncdb, the subscriber table does not yet exist. That's where the failure was happening. Then the database was left in a state it wasn't happy with, and it went and made everyone else miserable.

Now the database should stay happy. But you should run `python website/manage.py syncsubscribers` after the migrations. Check out https://github.com/codeforamerica/councilmatic/blob/master/local-councilmatic-sample/README.md