Closed frinzekt closed 3 years ago
For production standard, flask should be served with request workers as seen in https://flask.palletsprojects.com/en/2.0.x/deploying/wsgi-standalone/
Currently, the production version just uses flask run a development server of flask. See setup at https://github.com/UWA-CITS3200-18-2021/ReSQ/blob/main/docker/app/runtime.sh#L66
flask run
This may be related to the issue with #53. When request workers are used, database connections automatically get discarded after the running process of a request worker (30 seconds by default as per https://devcenter.heroku.com/articles/python-gunicorn#:~:text=Worker%20timeouts,with%20a%20lower%20timeout%20configuration.)
Closed by #57
frinzekt
commented
3 years ago frinzekt
commented
3 years ago
Basic Information
For production standard, flask should be served with request workers as seen in https://flask.palletsprojects.com/en/2.0.x/deploying/wsgi-standalone/
Other Information
Currently, the production version just uses
flask runa development server of flask. See setup at https://github.com/UWA-CITS3200-18-2021/ReSQ/blob/main/docker/app/runtime.sh#L66This may be related to the issue with #53. When request workers are used, database connections automatically get discarded after the running process of a request worker (30 seconds by default as per https://devcenter.heroku.com/articles/python-gunicorn#:~:text=Worker%20timeouts,with%20a%20lower%20timeout%20configuration.)