[GH-ISSUE #39] Does it make sense to get rid of "Use a production WSGI server instead" ? #8

New issue

Open

opened 2026-03-02 03:44:35 +03:00 by kerem · 0 comments

kerem commented

2026-03-02 03:44:35 +03:00

Owner

Originally created by @ieugen on GitHub (Jan 2, 2022).
Original GitHub issue: https://github.com/dignajar/another-ldap-auth/issues/39

Hi,

While running the docker version of the app I got:

 * Environment: production
   WARNING: This is a development server. Do not use it in a production deployment.
   Use a production WSGI server instead.

Googleing that (not a python dev) I got to the bellow solution - to use waitress - a production ready wsgi server.
I think others exist as well.

if __name__ == "__main__":
    from waitress import serve
    serve(app, host="0.0.0.0", port=8080)

https://stackoverflow.com/questions/51025893/flask-at-first-run-do-not-use-the-development-server-in-a-production-environmen

Originally created by @ieugen on GitHub (Jan 2, 2022). Original GitHub issue: https://github.com/dignajar/another-ldap-auth/issues/39 Hi, While running the docker version of the app I got: ``` * Environment: production WARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead. ``` Googleing that (not a python dev) I got to the bellow solution - to use waitress - a production ready wsgi server. I think others exist as well. ``` if __name__ == "__main__": from waitress import serve serve(app, host="0.0.0.0", port=8080) ``` https://stackoverflow.com/questions/51025893/flask-at-first-run-do-not-use-the-development-server-in-a-production-environmen