runner called waitress-serve, which can be used in development and in situations where the likes of PasteDeploy is not necessary: # Listen on both IPv4 and IPv6 on port 8041 waitress-serve --listen=*:8041 --listen=*:8041 myapp:wsgifunc # Listen on only IPv4 on port 8041 waitress-serve --port=8041 myapp:wsgifunc 1.1.1 Heroku Waitress can be used to serve WSGI apps on Heroku, include waitress in your requirements requirements.txt file a update the Procfile as following: web: waitress-serve \ --listen "*:$PORT" \ --trusted-proxy '*' \ --trusted-proxy-headers 'x-forwarded-for x-forwarded-proto x-forwarded-port' \ --log-un

runner called waitress-serve, which can be used in development and in situations where the likes of PasteDeploy is not necessary: # Listen on both IPv4 and IPv6 on port 8041 waitress-serve --listen=*:8041 --listen=*:8041 myapp:wsgifunc # Listen on only IPv4 on port 8041 waitress-serve --port=8041 myapp:wsgifunc 1.1.1 Heroku Waitress can be used to serve WSGI apps on Heroku, include waitress in your requirements requirements.txt file a update the Procfile as following: web: waitress-serve \ --listen "*:$PORT" \ --trusted-proxy '*' \ --trusted-proxy-headers 'x-forwarded-for x-forwarded-proto x-forwarded-port' \ --log-un

runner called waitress-serve, which can be used in development and in situations where the likes of PasteDeploy is not necessary: # Listen on both IPv4 and IPv6 on port 8041 waitress-serve --listen=*:8041 --listen=*:8041 myapp:wsgifunc # Listen on only IPv4 on port 8041 waitress-serve --port=8041 myapp:wsgifunc For more information on this, see waitress-serve. 1.2 Access Logging The WSGI design is modular. Waitress wrapper that wraps a sufficiently file-like object. It may do something fancier in the future. 1.9 waitress-serve New in version 0.8.4: Waitress comes bundled with a thin command-line wrapper around the waitress

runner called waitress-serve, which can be used in development and in situations where the likes of PasteDeploy is not necessary: # Listen on both IPv4 and IPv6 on port 8041 waitress-serve --listen=*:8041 --listen=*:8041 myapp:wsgifunc # Listen on only IPv4 on port 8041 waitress-serve --port=8041 myapp:wsgifunc 1.1.1 Heroku Waitress can be used to serve WSGI apps on Heroku, include waitress in your requirements requirements.txt file and update the Procfile as following: web: waitress-serve \ --listen "*:$PORT" \ --trusted-proxy '*' \ --trusted-proxy-headers 'x-forwarded-for x-forwarded-proto x-forwarded-port' \ --log-

runner called waitress-serve, which can be used in development and in situations where the likes of PasteDeploy is not necessary: # Listen on both IPv4 and IPv6 on port 8041 waitress-serve --listen=*:8041 --listen=*:8041 myapp:wsgifunc # Listen on only IPv4 on port 8041 waitress-serve --port=8041 myapp:wsgifunc For more information on this, see waitress-serve. 1.2 Access Logging The WSGI design is modular. Waitress wrapper that wraps a sufficiently file-like object. It may do something fancier in the future. 1.9 waitress-serve New in version 0.8.4: Waitress comes bundled with a thin command-line wrapper around the waitress

where Gunicorn and uWSGI don’t work yet you can use Waitress server $ pip install waitress $ waitress-serve --port=8000 things:app Then, in another terminal: $ curl localhost:8000/things Curl is a bit used in lieu of Gunicorn, since the latter doesn’t work under Windows: $ pip install waitress $ waitress-serve --port=8000 look.app Now, in a different terminal, try querying the running app with curl:

where Gunicorn and uWSGI don’t work yet you can use Waitress server $ pip install waitress $ waitress-serve --port=8000 things:app Then, in another terminal: $ curl localhost:8000/things Curl is a bit used in lieu of Gunicorn, since the latter doesn’t work under Windows: $ pip install waitress $ waitress-serve --port=8000 look.app Now, in a different terminal, try querying the running app with curl:

where Gunicorn and uWSGI don’t work yet you can use Waitress server $ pip install waitress $ waitress-serve --port=8000 things:app Then, in another terminal: $ curl localhost:8000/things Curl is a bit used in lieu of Gunicorn, since the latter doesn’t work under Windows: $ pip install waitress $ waitress-serve --port=8000 look:app Now, in a different terminal, try querying the running app with curl:

where Gunicorn and uWSGI don’t work yet you can use Waitress server $ pip install waitress $ waitress-serve --port=8000 things:app Then, in another terminal: $ curl localhost:8000/things Curl is a bit used in lieu of Gunicorn, since the latter doesn’t work under Windows: $ pip install waitress $ waitress-serve --port=8000 look:app Now, in a different terminal, try querying the running app with curl:

where Gunicorn and uWSGI don’t work yet you can use Waitress server $ pip install waitress $ waitress-serve --port=8000 things:app Then, in another terminal: $ curl localhost:8000/things Curl is a bit used in lieu of Gunicorn, since the latter doesn’t work under Windows: $ pip install waitress $ waitress-serve --port=8000 look:app Now, in a different terminal, try querying the running app with curl: