- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 185 for Uvicorn (0.04 sec)
-
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.
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Sat Nov 09 16:39:20 UTC 2024 - 5.3K bytes - Viewed (0) -
docs/es/docs/benchmarks.md
* Si estás comparando Uvicorn, compáralo con Daphne, Hypercorn, uWSGI, etc. Servidores de aplicaciones. * **Starlette**: * Tendrá el siguiente mejor rendimiento, después de Uvicorn. De hecho, Starlette usa Uvicorn para ejecutarse. Así que probablemente solo pueda ser "más lento" que Uvicorn por tener que ejecutar más código.
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Mon Dec 30 17:46:44 UTC 2024 - 3.7K bytes - Viewed (0) -
docs/en/docs/benchmarks.md
* If you are comparing Uvicorn, compare it against Daphne, Hypercorn, uWSGI, etc. Application servers. * **Starlette**: * Will have the next best performance, after Uvicorn. In fact, Starlette uses Uvicorn to run. So, it probably can only get "slower" than Uvicorn by having to execute more code. * But it provides you the tools to build simple web applications, with routing based on paths, etc.
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Sun Aug 31 09:15:41 UTC 2025 - 3.5K bytes - Viewed (0) -
docs/fr/docs/deployment/manually.md
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Sat Nov 09 16:39:20 UTC 2024 - 5.3K 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
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Mon Nov 18 02:25:44 UTC 2024 - 10.3K bytes - Viewed (0) -
docs/de/docs/advanced/behind-a-proxy.md
### Bereitstellung des `root_path` Um dies zu erreichen, können Sie die Kommandozeilenoption `--root-path` wie folgt verwenden: <div class="termy"> ```console $ uvicorn main:app --root-path /api/v1 <span style="color: green;">INFO</span>: Uvicorn running on http://127.0.0.1:8000 (Press CTRL+C to quit) ```
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Mon Nov 18 02:25:44 UTC 2024 - 13K bytes - Viewed (0) -
docs/es/docs/advanced/behind-a-proxy.md
### Proporcionando el `root_path` Para lograr esto, puedes usar la opción de línea de comandos `--root-path` como: <div class="termy"> ```console $ fastapi run main.py --root-path /api/v1 <span style="color: green;">INFO</span>: Uvicorn running on http://127.0.0.1:8000 (Press CTRL+C to quit) ``` </div>
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Mon Dec 30 18:26:57 UTC 2024 - 12.1K bytes - Viewed (0) -
docs/ru/docs/tutorial/first-steps.md
Это единая точка входа для создания и взаимодействия с API. Именно к этой переменной `app` обращается `uvicorn` в команде: <div class="termy"> ```console $ uvicorn main:app --reload <span style="color: green;">INFO</span>: Uvicorn running on http://127.0.0.1:8000 (Press CTRL+C to quit) ``` </div> Если создать такое приложение:
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Mon Nov 18 02:25:44 UTC 2024 - 12.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).
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Sat Nov 09 16:39:20 UTC 2024 - 37.4K bytes - Viewed (0) -
docs/fr/docs/tutorial/first-steps.md
Ce sera le point principal d'interaction pour créer toute votre API. Cette `app` est la même que celle à laquelle fait référence `uvicorn` dans la commande : <div class="termy"> ```console $ uvicorn main:app --reload <span style="color: green;">INFO</span>: Uvicorn running on http://127.0.0.1:8000 (Press CTRL+C to quit) ``` </div> Si vous créez votre app avec :
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Sat Nov 09 16:39:20 UTC 2024 - 10.1K bytes - Viewed (0)