I've provisioned the free hobby tier of the postgres add-on in Heroku.
That should set the proper environment variable automatically in those environments, and Flask-SQLAlchemy should just start using that persistent database.
I've also implemented a new deploy CLI command which runs the database migrations and injects the sample meters, poets, and poems if they're not already in the database... without having to use the /reset route, which has been changed to do the same thing (instead of using db.create_all().
I've provisioned the free hobby tier of the postgres add-on in Heroku. That should set the proper environment variable automatically in those environments, and Flask-SQLAlchemy should just start using that persistent database.
I've also implemented a new
deployCLI command which runs the database migrations and injects the sample meters, poets, and poems if they're not already in the database... without having to use the/resetroute, which has been changed to do the same thing (instead of usingdb.create_all().This fixes #103.