[Flask] Why flask.run() is not for production environment

Samuel Harmer me at samuelharmer.com
Mon Jul 10 04:19:22 EDT 2017

Dear Deepak,

A quick Google for "flask deployment wsgi" gets you to
http://flask.pocoo.org/docs/0.12/deploying/ which describes a number of
options. In short, serving fast and safe HTTP to the www is a significant
challenge. `.run()` works but has not had the same effort put into www
engineering than dedicated web server projects have.

Kind regards,
Samuel Harmer

On 10 July 2017 at 09:10, Deepak Jose <deepakpjose at gmail.com> wrote:

> Hi Team,
> Can someone explain me why run() is not good for production environment?
> All the examples I have seen for flask use run. Can someone help me to
> understand why it is not recommended and
> how we have to deploy our app then? The :ref:'deployment' can be found
> where?
> Excerpts from flask documentation for run:
> def run(self, host=None, port=None, debug=None, **options):
> """Runs the application on a local development server.
> *Do not use ``run()`` in a production setting. It is not intended to*
> *meet security and performance requirements for a production server.*
> *Instead, see :ref:`deployment` for WSGI server recommendations.*Thanks,
> Deepak
> _______________________________________________
> Flask mailing list
> Flask at python.org
> https://mail.python.org/mailman/listinfo/flask
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/flask/attachments/20170710/f31cbc7b/attachment.html>

More information about the Flask mailing list