- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 151 for Uvicorn (1.23 sec)
-
docs/en/docs/deployment/server-workers.md
## Install Gunicorn and Uvicorn <div class="termy"> ```console $ pip install "uvicorn[standard]" gunicorn ---> 100% ``` </div> That will install both Uvicorn with the `standard` extra packages (to get high performance) and Gunicorn. ## Run Gunicorn with Uvicorn Workers Then you can run Gunicorn with: <div class="termy"> ```console
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu Apr 18 19:53:19 GMT 2024 - 9.1K bytes - Viewed (0) -
docs/em/docs/deployment/server-workers.md
& **Uvicorn** ✔️ **🐁-🔗 👨🏭 🎓**. ⚙️ 👈 🌀, 🐁 🔜 🚫 **🛠️ 👨💼**, 👂 🔛 **⛴** & **📢**. & ⚫️ 🔜 **📶** 📻 👨🏭 🛠️ 🏃 **Uvicorn 🎓**. & ⤴️ 🐁-🔗 **Uvicorn 👨🏭** 🎓 🔜 🈚 🏭 📊 📨 🐁 🔫 🐩 FastAPI ⚙️ ⚫️. ## ❎ 🐁 & Uvicorn <div class="termy"> ```console $ pip install "uvicorn[standard]" gunicorn ---> 100% ``` </div>
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu Apr 18 19:53:19 GMT 2024 - 8.2K bytes - Viewed (0) -
docs/ja/docs/deployment/server-workers.md
そして**Uvicorn**には**Gunicorn互換のワーカークラス**があります。 この組み合わせで、Gunicornは**プロセスマネージャー**として動作し、**ポート**と**IP**をリッスンします。そして、**Uvicornクラス**を実行しているワーカー・プロセスに通信を**転送**します。 そして、Gunicorn互換の**Uvicornワーカー**クラスが、FastAPIが使えるように、Gunicornから送られてきたデータをASGI標準に変換する役割を担います。 ## GunicornとUvicornをインストールする <div class="termy"> ```console $ pip install "uvicorn[standard]" gunicorn ---> 100% ``` </div>
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu Apr 18 19:53:19 GMT 2024 - 11.2K bytes - Viewed (0) -
docs/de/docs/deployment/manually.md
# Einen Server manuell ausführen – Uvicorn Das Wichtigste, was Sie zum Ausführen einer **FastAPI**-Anwendung auf einer entfernten Servermaschine benötigen, ist ein ASGI-Serverprogramm, wie **Uvicorn**. Es gibt 3 Hauptalternativen: * <a href="https://www.uvicorn.org/" class="external-link" target="_blank">Uvicorn</a>: ein hochperformanter ASGI-Server.
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Sat Mar 30 20:16:35 GMT 2024 - 5.4K bytes - Viewed (0) -
docs/de/docs/deployment/server-workers.md
## Gunicorn und Uvicorn installieren <div class="termy"> ```console $ pip install "uvicorn[standard]" gunicorn ---> 100% ``` </div> Dadurch wird sowohl Uvicorn mit zusätzlichen `standard`-Packages (um eine hohe Leistung zu erzielen) als auch Gunicorn installiert. ## Gunicorn mit Uvicorn-Workern ausführen Dann können Sie Gunicorn ausführen mit:
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Sat Mar 30 18:19:25 GMT 2024 - 10.1K bytes - Viewed (0) -
docs/zh/docs/advanced/behind-a-proxy.md
它不要求访问 `http://127.0.0.1:800/api/v1/app`。 Uvicorn 预期代理在 `http://127.0.0.1:8000/app` 访问 Uvicorn,而在顶部添加 `/api/v1` 前缀是代理要做的事情。 ## 关于移除路径前缀的代理 注意,移除路径前缀的代理只是配置代理的方式之一。 大部分情况下,代理默认都不会移除路径前缀。 (未移除路径前缀时)代理监听 `https://myawesomeapp.com` 等对象,如果浏览器跳转到 `https://myawesomeapp.com/api/v1/app`,且服务器(例如 Uvicorn)监听 `http://127.0.0.1:8000` 代理(未移除路径前缀) 会在同样的路径:`http://127.0.0.1:8000/api/v1/app` 访问 Uvicorn。 ## 本地测试 Traefik
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu Apr 18 19:53:19 GMT 2024 - 10.4K bytes - Viewed (0) -
docs/zh/docs/deployment/server-workers.md
**Uvicorn** 有一个 Gunicorn 兼容的worker类。 使用这种组合,Gunicorn 将充当 **进程管理器**,监听 **端口** 和 **IP**。 它会将通信**传输**到运行**Uvicorn类**的worker进程。 然后与Gunicorn兼容的**Uvicorn worker**类将负责将Gunicorn发送的数据转换为ASGI标准以供FastAPI使用。 ## 安装 Gunicorn 和 Uvicorn <div class="termy"> ```console $ pip install "uvicorn[standard]" gunicorn ---> 100% ``` </div>
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu Apr 18 19:53:19 GMT 2024 - 8.7K bytes - Viewed (0) -
docs/ru/docs/deployment/manually.md
# Запуск сервера вручную - Uvicorn Для запуска приложения **FastAPI** на удалённой серверной машине вам необходим программный сервер, поддерживающий протокол ASGI, такой как **Uvicorn**. Существует три наиболее распространённые альтернативы: * <a href="https://www.uvicorn.org/" class="external-link" target="_blank">Uvicorn</a>: высокопроизводительный ASGI сервер.
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Wed Apr 03 16:22:47 GMT 2024 - 7.8K bytes - Viewed (0) -
docs/de/docs/deployment/docker.md
In einem solchen Szenario möchten Sie wahrscheinlich **einen einzelnen (Uvicorn-)Prozess pro Container** haben, da Sie die Replikation bereits auf Cluster ebene durchführen würden. In diesem Fall möchten Sie also **nicht** einen Prozessmanager wie Gunicorn mit Uvicorn-Workern oder Uvicorn mit seinen eigenen Uvicorn-Workern haben. Sie möchten nur einen **einzelnen Uvicorn-Prozess** pro Container haben (wahrscheinlich aber mehrere Container).
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Sat Mar 30 18:19:17 GMT 2024 - 38.9K bytes - Viewed (0) -
docs/pt/docs/deployment/docker.md
Nesse tipo de cenário, provavelmente você desejará ter **um único processo (Uvicorn) por contêiner**, pois já estaria lidando com a replicação no nível do cluster. Então, nesse caso, você **não** desejará ter um gerenciador de processos como o Gunicorn com trabalhadores Uvicorn, ou o Uvicorn usando seus próprios trabalhadores Uvicorn. Você desejará ter apenas um **único processo Uvicorn** por contêiner (mas provavelmente vários contêineres).
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu Apr 18 19:53:19 GMT 2024 - 37.4K bytes - Viewed (0)