Issue #56: fix secret_key check in production configuration of resultsdb_frontend - libtaskotron

taskotron / libtaskotron

#56 fix secret_key check in production configuration of resultsdb_frontend

Closed: Fixed None Opened 10 years ago by tflink.

The check to make sure Flask's secret_key isn't the default for production config is being done before any configuration is loaded and thus, always fails. This is preventing deployment of resultsdb_frontend in a production environment and needs to be fixed.

I've written a patch to fix the issue:
{F1456}