The acception solution doesn't work for me.
Gunicorn is a pre-forking environment and apparently the Flask debugger doesn't work in a forking environment.
Attention
Even though the interactive debugger does not work in
forking environments (which makes it nearly impossible to use on
production servers) [...]
Even if you set app.debug = True
, you will still only get an empty page with the message Internal Server Error if you run with gunicorn testserver:app
. The best you can do with gunicorn is to run it with gunicorn --debug testserver:app
. That gives you the trace in addition to the Internal Server Error message. However, this is just the same text trace that you see in the terminal and not the Flask debugger.
Adding the if __name__ ...
section to the testserver.py and running python testserver.py
to start the server in development gets you the Flask debugger. In other words, don't use gunicorn in development if you want the Flask debugger.
app = Flask(__name__)
app.config['DEBUG'] = True
if __name__ == '__main__':
app.run()
Tip for Heroku users:
Personally I still like to use foreman start
, instead of python testserver.py
since it sets up all the env variables for me. To get this to work:
Contents of Procfile
web: bin/web
Contents of bin/web
, file is relative to project root
#!/bin/sh
if [ "$FLASK_ENV" == "development" ]; then
python app.py
else
gunicorn app:app -w 3
fi
In development, create a .env
file relative to project root with the following contents (docs here)
FLASK_ENV=development
DEBUG=True
Also, dont forget to change the app.config['DEBUG']...
line in testserver.py
to something that won't run Flask in debug mode in production.
app.config['DEBUG'] = os.environ.get('DEBUG', False)
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…