Search Options

Results per page
Sort
Preferred Languages
Advance

Results 41 - 50 of 222 for uvicorn (0.04 sec)

  1. docs/es/docs/deployment/server-workers.md

    </pre>
    ```
    
    </div>
    
    ////
    
    //// tab | `uvicorn`
    
    Si prefieres usar el comando `uvicorn` directamente:
    
    <div class="termy">
    
    ```console
    $ uvicorn main:app --host 0.0.0.0 --port 8080 --workers 4
    <font color="#A6E22E">INFO</font>:     Uvicorn running on <b>http://0.0.0.0:8080</b> (Press CTRL+C to quit)
    Registered: Sun Sep 07 07:19:17 UTC 2025
    - Last Modified: Mon Dec 30 18:26:57 UTC 2024
    - 8.9K bytes
    - Viewed (0)
  2. docs/pt/docs/deployment/server-workers.md

    ```
    
    </div>
    
    ////
    
    //// tab | `uvicorn`
    
    Se você preferir usar o comando `uvicorn` diretamente:
    
    <div class="termy">
    
    ```console
    $ uvicorn main:app --host 0.0.0.0 --port 8080 --workers 4
    <font color="#A6E22E">INFO</font>:     Uvicorn running on <b>http://0.0.0.0:8080</b> (Press CTRL+C to quit)
    Registered: Sun Sep 07 07:19:17 UTC 2025
    - Last Modified: Thu Jan 09 20:41:07 UTC 2025
    - 8.5K bytes
    - Viewed (0)
  3. docs/pt/docs/advanced/behind-a-proxy.md

    ### Fornecendo o `root_path`
    
    Para conseguir isso, você pode usar a opção de linha de comando `--root-path` assim:
    
    <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: Sat Nov 09 16:39:20 UTC 2024
    - 12.2K bytes
    - Viewed (0)
  4. 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).
    
    Registered: Sun Sep 07 07:19:17 UTC 2025
    - Last Modified: Sat Nov 09 16:39:20 UTC 2024
    - 38.9K bytes
    - Viewed (0)
  5. docs/vi/docs/tutorial/first-steps.md

    Đây sẽ là điểm cốt lõi để tạo ra tất cả API của bạn.
    
    `app` này chính là điều được nhắc tới bởi `uvicorn` trong câu lệnh:
    
    <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>
    
    Nếu bạn tạo ứng dụng của bạn giống như:
    
    Registered: Sun Sep 07 07:19:17 UTC 2025
    - Last Modified: Sun Nov 10 16:58:43 UTC 2024
    - 11K bytes
    - Viewed (0)
  6. docs/ja/docs/benchmarks.md

        * もしUvicornを比較する場合は、Daphne、Hypercorn、uWSGIなどのアプリケーションサーバーと比較してください。
    * **Starlette**:
        * Uvicornに次ぐ性能を持つでしょう。実際、StarletteはUvicornを使用しています。だから、より多くのコードを実行する必要があり、Uvicornよりも「遅く」なってしまうだけなのです。
        * しかし、パスベースのルーティングなどのシンプルなWEBアプリケーションを構築する機能を提供します。
        * もしStarletteを比較する場合は、Sanic、Flask、DjangoなどのWEBフレームワーク (もしくはマイクロフレームワーク) と比較してください。
    * **FastAPI**:
        * StarletteがUvicornを使っているのと同じで、**FastAPI**はStarletteを使っており、それより速くできません。
    Registered: Sun Sep 07 07:19:17 UTC 2025
    - Last Modified: Sat Oct 17 18:43:43 UTC 2020
    - 4.4K bytes
    - Viewed (0)
  7. docs/ko/docs/deployment/docker.md

    ### 단일 프로세스를 가지는 컨테이너
    
    이 시나리오의 경우, 여러분은 이미 클러스터 레벨에서 복제를 다루고 있을 것이므로 **컨테이너 당 단일 (Uvicorn) 프로세스**를 가지고자 할 것입니다.
    
    따라서, 여러분은 Gunicorn 이나 Uvicorn 워커, 또는 Uvicorn 워커를 사용하는 Uvicorn 매니저와 같은 프로세스 매니저를 가지고 싶어하지 **않을** 것입니다. 여러분은 컨테이너 당 **단일 Uvicorn 프로세스**를 가지고 싶어할 것입니다 (그러나 아마도 다중 컨테이너를 가질 것입니다).
    
    이미 여러분이 클러스터 시스템을 관리하고 있으므로, (Uvicorn 워커를 관리하는 Gunicorn 이나 Uvicorn 처럼) 컨테이너 내에 다른 프로세스 매니저를 가지는 것은 **불필요한 복잡성**만 더하게 될 것입니다.
    
    ### 다중 프로세스를 가지는 컨테이너와 특수한 경우들
    Registered: Sun Sep 07 07:19:17 UTC 2025
    - Last Modified: Sat Nov 09 16:39:20 UTC 2024
    - 42.7K bytes
    - Viewed (0)
  8. docs/de/docs/deployment/concepts.md

    * **Gunicorn**, welches **Uvicorn-Worker** managt
        * Gunicorn wäre der **Prozessmanager**, der die **IP** und den **Port** überwacht, die Replikation würde durch **mehrere Uvicorn-Workerprozesse** erfolgen
    * **Uvicorn**, welches **Uvicorn-Worker** managt
        * Ein Uvicorn-**Prozessmanager** würde der **IP** am **Port** lauschen, und er würde **mehrere Uvicorn-Workerprozesse** starten.
    Registered: Sun Sep 07 07:19:17 UTC 2025
    - Last Modified: Sun May 11 13:37:26 UTC 2025
    - 20.6K bytes
    - Viewed (0)
  9. docs/uk/docs/tutorial/index.md

    Щоб запустити будь-який із прикладів, скопіюйте код у файл `main.py` і запустіть `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)
    <span style="color: green;">INFO</span>:     Started reloader process [28720]
    Registered: Sun Sep 07 07:19:17 UTC 2025
    - Last Modified: Tue Aug 06 04:48:30 UTC 2024
    - 4.4K bytes
    - Viewed (0)
  10. docs/en/docs/tutorial/debugging.md

    # Debugging { #debugging }
    
    You can connect the debugger in your editor, for example with Visual Studio Code or PyCharm.
    
    ## Call `uvicorn` { #call-uvicorn }
    
    In your FastAPI application, import and run `uvicorn` directly:
    
    {* ../../docs_src/debugging/tutorial001.py hl[1,15] *}
    
    ### About `__name__ == "__main__"` { #about-name-main }
    
    The main purpose of the `__name__ == "__main__"` is to have some code that is executed when your file is called with:
    Registered: Sun Sep 07 07:19:17 UTC 2025
    - Last Modified: Sun Aug 31 09:15:41 UTC 2025
    - 2.5K bytes
    - Viewed (0)
Back to top