Deployment in production In your production system, you may want to deploy the web applications with some WSGI/ASGI servers such as uWSGI, Gunicorn, and Uvicorn. Since PyWebIO applications store session state to integrate PyWebIO applications into exist- ing Python Web project. The wsgi_app() and asgi_app() is used to get the WSGI or ASGI app for running PyWebIO applications. This is helpful when you don’t don’t want to start server with the Web framework built-in’s. For example, you want to use other WSGI server, or you are deploying app in a cloud environment. Note that only Flask, Django and FastApi backend

Deployment in production In your production system, you may want to deploy the web applications with some WSGI/ASGI servers such as uWSGI, Gunicorn, and Uvicorn. Since PyWebIO applications store session state to integrate PyWebIO applications into exist- ing Python Web project. The wsgi_app() and asgi_app() is used to get the WSGI or ASGI app for running PyWebIO applications. This is helpful when you don’t don’t want to start server with the Web framework built-in’s. For example, you want to use other WSGI server, or you are deploying app in a cloud environment. Note that only Flask, Django and FastApi backend

Deployment in production In your production system, you may want to deploy the web applications with some WSGI/ASGI servers such as uWSGI, Gunicorn, and Uvicorn. Since PyWebIO applications store session state to integrate PyWebIO applications into exist- ing Python Web project. The wsgi_app() and asgi_app() is used to get the WSGI or ASGI app for running PyWebIO applications. This is helpful when you don’t don’t want to start server with the Web framework built-in’s. For example, you want to use other WSGI server, or you are deploying app in a cloud environment. Note that only Flask, Django and FastApi backend

Deployment in production In your production system, you may want to deploy the web applications with some WSGI/ASGI servers such as uWSGI, Gunicorn, and Uvicorn. Since PyWebIO applications store session state to integrate PyWebIO applications into exist- ing Python Web project. The wsgi_app() and asgi_app() is used to get the WSGI or ASGI app for running PyWebIO applications. This is helpful when you don’t don’t want to start server with the Web framework built-in’s. For example, you want to use other WSGI server, or you are deploying app in a cloud environment. Note that only Flask, Django and FastApi backend

to integrate PyWebIO applications into exist- ing Python Web project. The wsgi_app() and asgi_app() is used to get the WSGI or ASGI app for running PyWebIO applications. This is helpful when you don’t don’t want to start server with the Web framework built-in’s. For example, you want to use other WSGI server, or you are deploying app in a cloud environment. Note that only Flask, Django and FastApi backend version 1.2: Added the static_dir parameter in start_server(). Changed in version 1.3: Added the wsgi_app() and asgi_app(). Tornado support There are two protocols (WebSocket and HTTP) can be used to

to integrate PyWebIO applications into exist- ing Python Web project. The wsgi_app() and asgi_app() is used to get the WSGI or ASGI app for running PyWebIO applications. This is helpful when you don’t don’t want to start server with the Web framework built-in’s. For example, you want to use other WSGI server, or you are deploying app in a cloud environment. Note that only Flask, Django and FastApi backend version 1.2: Added the static_dir parameter in start_server(). Changed in version 1.3: Added the wsgi_app() and asgi_app(). Tornado support There are two protocols (WebSocket and HTTP) can be used to

to integrate PyWebIO applications into exist- ing Python Web project. The wsgi_app() and asgi_app() is used to get the WSGI or ASGI app for running PyWebIO applications. This is helpful when you don’t don’t want to start server with the Web framework built-in’s. For example, you want to use other WSGI server, or you are deploying app in a cloud environment. Note that only Flask, Django and FastApi backend version 1.2: Added the static_dir parameter in start_server(). Changed in version 1.3: Added the wsgi_app() and asgi_app(). 4.5. pywebio.platform — Deploy applications 55 PyWebIO, Release 1.4.0 Tornado

to integrate PyWebIO applications into exist- ing Python Web project. The wsgi_app() and asgi_app() is used to get the WSGI or ASGI app for running PyWebIO applications. This is helpful when you don’t don’t want to start server with the Web framework built-in’s. For example, you want to use other WSGI server, or you are deploying app in a cloud environment. Note that only Flask, Django and FastApi backend version 1.2: Added the static_dir parameter in start_server(). Changed in version 1.3: Added the wsgi_app() and asgi_app(). Tornado support There are two protocols (WebSocket and HTTP) can be used to

to integrate PyWebIO applications into exist- ing Python Web project. The wsgi_app() and asgi_app() is used to get the WSGI or ASGI app for running PyWebIO applications. This is helpful when you don’t don’t want to start server with the Web framework built-in’s. For example, you want to use other WSGI server, or you are deploying app in a cloud environment. Note that only Flask, Django and FastApi backend version 1.2: Added the static_dir parameter in start_server(). Changed in version 1.3: Added the wsgi_app() and asgi_app(). Tornado support There are two protocols (WebSocket and HTTP) can be used to

to integrate PyWebIO applications into exist- ing Python Web project. The wsgi_app() and asgi_app() is used to get the WSGI or ASGI app for running PyWebIO applications. This is helpful when you don’t don’t want to start server with the Web framework built-in’s. For example, you want to use other WSGI server, or you are deploying app in a cloud environment. Note that only Flask, Django and FastApi backend version 1.2: Added the static_dir parameter in start_server(). Changed in version 1.3: Added the wsgi_app() and asgi_app(). Tornado support There are two protocols (WebSocket and HTTP) can be used to