Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Startup the flask dev server the correct way #26

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

kobemertens
Copy link

As indicated in the Flask documentation (https://flask.palletsprojects.com/en/2.3.x/server/#in-code) app.run is not the best way to run the flask dev server. It is better to run as flask run. This does not crash the server on errors, instead it logs and returns the error and stacktrace.

As indicated in the Flask documentation (https://flask.palletsprojects.com/en/2.3.x/server/#in-code) `app.run` is not the best way to run the flask dev server. It is better to run as `flask run`. This does not crash the server on errors, instead it logs and returns the error and stacktrace.
@kobemertens
Copy link
Author

Also appears to be related to #19. However I think this change is smaller, so it might be worth it to merge this one while investigating running with gunicorn

@madnificent
Copy link
Member

Thank you for the PR and also for referring to the related work of PR19. We have published a build of PR19 which may speed up that work. It may well be that we also want this to be merged in but given the attention the mu-python-template briefly has now, it seems worth to get PR19 tested and merged. We leave this open for the time being because it spun up the work and we might land PR26 (this PR) instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants