After further contemplation (.env)

I simplified the environment setup.
  + there is now an example-env which should be copied to .env and modified
  + then use autoenv or 'source .env' to set up local environment
  + these variables are also set as heroku config variables in the heroku config panel
using .env pattern from last commit + no heroku

Using the .env / example-env pattern from the last
commit universally.  Also removing heroku cruft
from a bunch of these projects that don't really
need it.
garage: flask-login + flask-oid

Got a version of this working where you can sign on with Google
or Yahoo OID.  The user search key is still oid provided email which is sub
optimal.  Rather switch to oid unique address.
moving dir
refactored sqlite version of messagr

+ use flask-sqlalchemy
+ seemed like a better practice to import entire models namespace
+ corrected db file tmp path
removing
readme
readmes
Trying to make this area more useful

+ Autoenv is confusing, so I'm removing references to it.
+ Moving requirements.txt individually to folders, as I think I'm moving towards putting all of this on heroku.
heroku setup add/remove

My general rule for heroku here is it is ok to put on heroku if:
  + app has no database
  + app has database and does authentication and authorization

Generally not OK to put on heroku if
  + app is single user and has database
  + app has databse doesn't both authenticate and authorize.
Let's have just one version of messager

Set up the database in the environment. It is a one line
change to swap from pgsql to sqlite.
links to deployed heroku apps.