SQLALCHEMY_TEST_DATABASE_URI is fine for a name, but personally, I would go with SQLALCHEMY_DATABASE_URI_TEST whenever I have a variable that has an environment as part of the name. If this is done consistently, this allows for a configuration pattern where can set un-versioned defaults, but then provide per-environment values by trying to find an equivalent var with the environment appended.

[tildeee]

SQLALCHEMY_TEST_DATABASE_URI is fine for a name, but personally, I would go with SQLALCHEMY_DATABASE_URI_TEST whenever I have a variable that has an environment as part of the name. If this is done consistently, this allows for a configuration pattern where can set un-versioned defaults, but then provide per-environment values by trying to find an equivalent var with the environment appended.

We don't really need this here (the test db is largely a one off, and if we had staging/production, we would be supplying an entirely separate environment configuration (probably through a dashboard), so we definitely do NOT need to change this, but I wanted to mention it.

Originally posted by @anselrognlie in #11 (comment)